{"id":"OESA-2026-4851","summary":"curl security update","details":"cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.\r\n\r\nSecurity Fix(es):\n\nWhen curl is built with GnuTLS, a malicious WebSocket server can make curl\nsend memory past its send buffer. This is due to an out of bounds read\nfollowing when `gnutls_record_send()` returns a number of bytes sent **greater\nthan the number of bytes it was given to send**. GnuTLS does that after a\nblocked send.(CVE-2026-107928)\n\nSetting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication,\ncontrary to expectations and documentation. A subsequent transfer on the same\nhandle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL\nisset next, leaking state information.(CVE-2026-86409)\n\nA flaw in the curl command line tool's logic makes it only set SSH host\nverification options when interacting directly using SFTP or SCP, and not as a\nresult of following a redirect.(CVE-2026-86410)\n\nAn HTTP proxy can trick libcurl into sending the origin's credentials (Basic\npassword, or a Negotiate/Kerberos ticket) to the proxy itself, by answering\nthe `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the\nexpected 407 `Proxy-Authenticate:`.(CVE-2026-86414)\n\nImporting a `includeSubDomains` parent HSTS entry before a longer-lived child\nentry, silently drops the child. Consequently, when the parent expires, the\nchild's valid HSTS policy is lost, causing curl to issue unencrypted HTTP\nrequests rather than upgrading to HTTPS.(CVE-2026-87862)\n\nAn authenticated HTTPS origin can supply an HSTS `max-age` value that the\nparser accepts, but time serialization later fails to process. On 64-bit\nsystems, extreme max-age values compute an absolute expiry within standard\ntime integer limits that exceeds calendar time structure bounds. During cache\nsaves, the original HSTS file is truncated before writing a temporary\nreplacement; when serialization fails, the temporary file is deleted, leaving\nan empty or partial cache. Because the save error is silently ignored during\ncleanup, curl exits successfully despite the data loss.(CVE-2026-87863)\n\nEnabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in\nthe `IMAP APPEND {N}` literal while transmitting line-ending expanded data.\nThe server reads only $N$ bytes for the payload, causing the remaining\noverflow bytes to be interpreted and executed as pipelined IMAP commands\nwithin the authenticated session.(CVE-2026-87864)\n\nWhen libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated\ninitial entry can cause host key validation to report a key *mismatch* as a\n*missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.(CVE-2026-87865)\n\nWhen built with wolfSSL, curl can successfully validate a pinned public key\nhash against a key the TLS peer does not possess. During the TLS handshake,\nwolfSSL validates the connection, but curl's subsequent re-parsing of the same\ncertificate - tricked by a manipulated validity length field - extracts and\nmatches a different embedded key, incorrectly authorizing the pinned public\nkey.(CVE-2026-87866)\n\nWhen writing a long cookie name and value to a Netscape cookie jar, a remote\nHTTP server can make `curl` write a record that exceeds its line-length\nparsing limit. Consequently, any subsequent `curl` invocation reading from\nthat same cookie jar using `--cookie` silently aborts parsing prematurely upon\nencountering the too long line, ignoring all subsequent valid cookies in the\nfile.(CVE-2026-92386)\n\nWhen an FTP wildcard `LIST` operation fails, libcurl omits the restoration\npath meant for successful listings, leaving the write callback set to the\ninternal listing parser and the write callback data pointing directly to the\neasy handle. Subsequent reuse of this handle triggers an immediate crash, and\ncloning it via `curl_easy_duphandle()` copies this corrupted state into the\nduplicate. If the original handle is subsequently freed, executing a transfer\non the cloned handle causes a heap use-after-free read against the dangling\nhandle reference; alternatively, reusing the original or cloned handle while\nchanging only  `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`)\nresults in type confusion, forcing the internal parser to interpret incoming\nserver response bytes into memory at the application-supplied write data\npointer.(CVE-2026-92388)\n\nlibcurl's TFTP state machine fails to validate state transitions against the\nrequested transfer direction, accepting opening server responses for both\nreads and writes interchangeably. A malicious TFTP server can respond to a\ndownload request in a way that forces the client into transmit mode, prompting\nlibcurl to consume and transmit data from the handle's persistent\n`CURLOPT_READDATA` pointer - including data remaining from unrelated prior\noperations, such as an HTTP POST request executed on a reused handle.(CVE-2026-92389)\n\nWhen invoked with `--remote-header-name` (`-J`), curl fails to preserve its\ndocumented anti-clobbering protection if an intermediate 103 Early Hints\nresponse precedes the final HTTP response, or if an `ETag` header is processed\nbefore `Content-Disposition` under `--etag-save`. This flaw allows an HTTP(S)\nserver to overwrite an existing local file specified in the\n`Content-Disposition` header despite the presence of the `-J` non-overwrite\nconstraint.(CVE-2026-92390)\n\nA deeply nested multipart MIME structure constructed via the public API causes\na stack overflow in libcurl during normal cleanup operations. An excessive\nrecursion depth within `curl_mime_free` leads to unbounded stack frame\nallocation during structure traversal, ultimately crashing the host process.(CVE-2026-92391)\n\nlibcurl could accidentally return a URL for `curl_easy_getinfo()`'s\n`CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither\nthe URL provided to libcurl nor the redirected URL did.(CVE-2026-94266)","modified":"2026-11-11T12:45:12.569121574Z","published":"2026-11-11T12:26:50Z","upstream":["CVE-2026-107928","CVE-2026-86409","CVE-2026-86410","CVE-2026-86414","CVE-2026-87862","CVE-2026-87863","CVE-2026-87864","CVE-2026-87865","CVE-2026-87866","CVE-2026-92386","CVE-2026-92388","CVE-2026-92389","CVE-2026-92390","CVE-2026-92391","CVE-2026-94266"],"database_specific":{"severity":"Medium"},"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4851"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107928"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86409"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86410"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-86414"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87862"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87863"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87864"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87865"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-87866"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92386"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92388"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92389"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92390"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92391"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94266"}],"affected":[{"package":{"name":"curl","ecosystem":"openEuler:24.03-LTS-SP1","purl":"pkg:rpm/openEuler/curl&distro=openEuler-24.03-LTS-SP1"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.0-38.oe2403sp1"}]}],"ecosystem_specific":{"x86_64":["curl-8.4.0-38.oe2403sp1.x86_64.rpm","curl-debuginfo-8.4.0-38.oe2403sp1.x86_64.rpm","curl-debugsource-8.4.0-38.oe2403sp1.x86_64.rpm","libcurl-8.4.0-38.oe2403sp1.x86_64.rpm","libcurl-devel-8.4.0-38.oe2403sp1.x86_64.rpm"],"aarch64":["curl-8.4.0-38.oe2403sp1.aarch64.rpm","curl-debuginfo-8.4.0-38.oe2403sp1.aarch64.rpm","curl-debugsource-8.4.0-38.oe2403sp1.aarch64.rpm","libcurl-8.4.0-38.oe2403sp1.aarch64.rpm","libcurl-devel-8.4.0-38.oe2403sp1.aarch64.rpm"],"noarch":["curl-help-8.4.0-38.oe2403sp1.noarch.rpm"],"src":["curl-8.4.0-38.oe2403sp1.src.rpm"]},"database_specific":{"source":"https://repo.openeuler.org/security/data/osv/OESA-2026-4851.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N"}]}