{"published_count":667,"discovered_count":673,"count":35,"cves":[{"cve_id":"CVE-2026-10536","title":"Use-after-free in HTTP/2 stream-dependency handling after curl_easy_reset()","description":"A use-after-free vulnerability exists in libcurl when an application\nconfigures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or\n`CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and\nfinally terminates the handle with `curl_easy_cleanup()`. During this final\ncleanup phase, libcurl attempts to access and modify an internal structure\nthat was already freed during the reset operation.","severity":"critical","cvss_score":9.8,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cwe":"CWE-416","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-10536","published":"2026-07-16"},{"cve_id":"CVE-2026-8925","title":"Double free of the GSASL context during SASL authentication cleanup","description":"The curl logic that works with SASL authentication could end up cleaning up\nthe GSASL context *twice* without clearing the pointer in between, making it\n`free()` the same pointer twice.","severity":"critical","cvss_score":9.8,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cwe":"CWE-415","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-8925","published":"2026-07-16"},{"cve_id":"CVE-2026-8926","title":"Password for another .netrc user sent when the URL specifies only a username","description":"When asking curl to use a `.netrc` file to find credentials and at the same\ntime specifying a URL with a username(without a password), like\n`https://user@example.com/`, curl could wrongly get and use the password for\n*another* user set in the `.netrc` file for that host if such a one exists and\nthere is no match for the specified user.","severity":"critical","cvss_score":9.1,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","cwe":"CWE-522","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-8926","published":"2026-07-16"},{"cve_id":"CVE-2026-8932","title":"Connection reuse ignores changed client certificate and private key TLS options","description":"libcurl would reuse a previously created connection even when some mTLS config\nrelated option had been changed that should have prohibited reuse.\n\nlibcurl keeps previously used connections in a connection pool for subsequent\ntransfers to reuse if one of them matches the setup. However, some TLS\nsettings related to client certificates were left out from the configuration\nmatch checks, making them match too easily. In particular options related to\nthe private key.","severity":"high","cvss_score":7.5,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","cwe":"CWE-305","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-8932","published":"2026-07-16"},{"cve_id":"CVE-2026-86410","title":"SSH host verification bypass when a redirect leads to SFTP or SCP","description":"A 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.","severity":"high","cvss_score":7.4,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","cwe":"CWE-297","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86410","published":"2026-10-14"},{"cve_id":"CVE-2026-80230","title":"OpenSSL pinning bypass","description":"When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable\nstandard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and\n`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on\nconnections established without a presented server certificate. Bypassing the\npinning check under these disabled-verification conditions allows\nunauthenticated connections to succeed when they should be rejected.","severity":"high","cvss_score":7.4,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","cwe":"CWE-295","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-80230","published":"2026-09-07"},{"cve_id":"CVE-2026-9547","title":"Known-host key type mismatch silently accepted via the CURLOPT_SSH_KEYFUNCTION callback","description":"When a libcurl-based application performs transfers via `SCP://` or `SFTP://`\nand utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an\nuntrusted server. This vulnerability occurs when a server presents a host key\ntype that does not match the specific key type already recorded for that host\nin the `known_hosts` file. Instead of rejecting the mismatch, the callback\nmechanism fails to properly enforce the restriction, allowing the connection\nto succeed without warning and risking a potential man-in-the-middle attack.","severity":"high","cvss_score":7.4,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","cwe":"CWE-297","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-9547","published":"2026-07-16"},{"cve_id":"CVE-2026-9080","title":"Use-after-free when curl_easy_pause() is called from the socket callback","description":"Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION`\ncallback triggers a use-after-free vulnerability, where libcurl attempts to\nstore a flag using a dangling struct pointer immediately after that pointer's\nmemory has been freed.","severity":"high","cvss_score":7.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","cwe":"CWE-416","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-9080","published":"2026-07-16"},{"cve_id":"CVE-2025-14017","title":"TLS options set on one thread apply globally in multi-threaded LDAPS transfers","description":"When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl,\nchanging TLS options in one thread would inadvertently change them globally\nand therefore possibly also affect other concurrently setup transfers.\n\nDisabling certificate verification for a specific transfer could\nunintentionally disable the feature for other threads as well.","severity":"medium","cvss_score":6.3,"cvss_vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","cwe":"CWE-567","product":"curl","reference_count":2,"url":"https://www.cve.org/CVERecord?id=CVE-2025-14017","published":"2026-01-08"},{"cve_id":"CVE-2026-92388","title":"FTP wildcard write callback mixup","description":"When 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.","severity":"medium","cvss_score":5.9,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H","cwe":"CWE-416","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92388","published":"2026-10-14"},{"cve_id":"CVE-2026-92387","title":"Infinite loop bypassing transfer timeouts when a server omits the final response line","description":"By permanently omitting the final control-response line, a malicious FTP,\nIMAP, POP3, or SMTP server can exploit libcurl and completely bypass its\nconfigured transfer timeout mechanism, indefinitely blocking all concurrent\ntransfers bound to the same multi-handle.","severity":"medium","cvss_score":5.9,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","cwe":"CWE-835","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92387","published":"2026-10-14"},{"cve_id":"CVE-2026-87864","title":"IMAP APPEND plus CRLF conversion command injection","description":"Enabling `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.","severity":"medium","cvss_score":5.9,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","cwe":"CWE-130","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-87864","published":"2026-10-14"},{"cve_id":"CVE-2026-86414","title":"Origin credentials sent to an HTTP proxy that answers CONNECT with 401 instead of 407","description":"An 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:`.","severity":"medium","cvss_score":5.9,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86414","published":"2026-10-14"},{"cve_id":"CVE-2025-13034","title":"Certificate pinning check skipped for QUIC connections with ngtcp2 and GnuTLS","description":"When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey`\nwith the curl tool,curl should check the public key of the server certificate\nto verify the peer.\n\nThis check was skipped in a certain condition that would then make curl allow\nthe connection without performing the proper check, thus not noticing a\npossible impostor. To skip this check, the connection had to be done with QUIC\nwith ngtcp2 built to use GnuTLS and the user had to explicitly disable the\nstandard certificate verification.","severity":"medium","cvss_score":5.9,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","cwe":"CWE-295","product":"curl","reference_count":2,"url":"https://www.cve.org/CVERecord?id=CVE-2025-13034","published":"2026-01-08"},{"cve_id":"CVE-2026-92391","title":"Stack overflow from unbounded recursion in curl_mime_free() on nested MIME parts","description":"A 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.","severity":"medium","cvss_score":5.3,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H","cwe":"CWE-674","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92391","published":"2026-10-14"},{"cve_id":"CVE-2025-14819","title":"Trust chain policy bypass via a cached CA store with a stale partial-chain option","description":"When doing TLS related transfers with reused easy or multi handles and\naltering the  `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally\nreuse a CA store cached in memory for which the partial chain option was\nreversed. Contrary to the user's wishes and expectations. This could make\nlibcurl find and accept a trust chain that it otherwise would not.","severity":"medium","cvss_score":5.3,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","cwe":"CWE-295","product":"curl","reference_count":2,"url":"https://www.cve.org/CVERecord?id=CVE-2025-14819","published":"2026-01-08"},{"cve_id":"CVE-2026-87863","title":"HSTS response erases persisted entries","description":"An 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.","severity":"medium","cvss_score":4.8,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-87863","published":"2026-10-14"},{"cve_id":"CVE-2026-87862","title":"HSTS cache import drops longer-lived child","description":"Importing 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.","severity":"medium","cvss_score":4.8,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-87862","published":"2026-10-14"},{"cve_id":"CVE-2026-86411","title":"FTP connection reuse inherits client-certificate","description":"An `ftp://` transfer configured with `CURLUSESSL_NONE` can reuse a pooled FTP\ncontrol connection that a previous easy handle upgraded with `STARTTLS` and\nauthenticated using a client certificate. The second handle performs neither a\nnew TLS handshake nor a new FTP login, so the server continues to authorize it\nunder the first handle's certificate identity.","severity":"medium","cvss_score":4.8,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":"CWE-488","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86411","published":"2026-10-14"},{"cve_id":"CVE-2026-82208","title":"Certificate validation bypass when wolfSSL's cached CA store overrides the SSL_CTX callback","description":"With the wolfSSL backend, when CA caching is enabled and an\n`CURLOPT_SSL_CTX_FUNCTION` callback replaces the trust store, libcurl can\nsilently reinstall the cached store after the callback returns. A certificate\ntrusted by the cached store but rejected by the callback-selected store is\nthen incorrectly accepted.","severity":"medium","cvss_score":4.8,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":"CWE-295","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-82208","published":"2026-09-07"},{"cve_id":"CVE-2026-80231","title":"Connection reuse ignoring a changed CURLSSLOPT_NATIVE_CA setting","description":"A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup\nfor a given hostname even when using a different Native CA Store setting\n(`CURLSSLOPT_NATIVE_CA`) than when the connection was created.","severity":"medium","cvss_score":4.8,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":"CWE-488","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-80231","published":"2026-09-07"},{"cve_id":"CVE-2025-11563","title":"Path traversal in wcurl via percent-encoded slashes","description":"URLs containing percent-encoded slashes (`/` or `\\`) can trick wcurl into\nsaving the output file outside of the current directory without the user\nexplicitly asking for it.\n\nThis flaw only affects the wcurl command line tool.","severity":"medium","cvss_score":4.6,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","cwe":"CWE-35","product":"curl","reference_count":2,"url":"https://www.cve.org/CVERecord?id=CVE-2025-11563","published":"2026-02-25"},{"cve_id":"CVE-2026-92386","title":"Cookie jar parsing aborted by an overlong cookie line written from a server-set cookie","description":"When 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.","severity":"medium","cvss_score":4.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","cwe":"CWE-1284","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92386","published":"2026-10-14"},{"cve_id":"CVE-2026-86412","title":"Cookie jar replaced by an empty file after a server sets an unloadable cookie","description":"A remote HTTP server can set a cookie that curl accepts and writes to a\nNetscape cookie jar but cannot reload. On the next invocation using the same\npath for `--cookie` and `--cookie-jar`, curl fails before connecting, then the\ncleanup procedure replaces the jar with an empty file, deleting cookies for\nunrelated domains.","severity":"medium","cvss_score":4.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","cwe":"CWE-754","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86412","published":"2026-10-14"},{"cve_id":"CVE-2025-10966","title":"Missing SFTP host verification with the wolfSSH backend","description":"curl's code for managing SSH connections when SFTP was done using the wolfSSH\npowered backend was flawed and missed host verification mechanisms.\n\nThis prevents curl from detecting MITM attackers and more.","severity":"medium","cvss_score":4.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-322","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2025-10966","published":"2025-11-07"},{"cve_id":"CVE-2026-94265","title":"Kerberos ticket sent to a foreign host after a redirect to a URL with userinfo","description":"When processing an HTTP redirect to a URL containing userinfo (a\n`username:password` component), curl might erroneously retain and re-transmit\nthe original host's HTTP Negotiate authentication state. Consequently, a\nmalicious server can trigger a redirect containing arbitrary userinfo to force\ncurl to send a freshly minted Kerberos ticket—generated using the ambient\nidentity of the client process to an untrusted third-party host, effectively\nbypassing the domain-scoping restrictions normally enforced by the absence of\n`--location-trusted`.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-200","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-94265","published":"2026-10-14"},{"cve_id":"CVE-2026-92390","title":"-J no-clobber guarantee bypassed with 103 early hints","description":"When 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.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","cwe":"CWE-73","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92390","published":"2026-10-14"},{"cve_id":"CVE-2026-92389","title":"TFTP direction confusion","description":"libcurl'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.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-200","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-92389","published":"2026-10-14"},{"cve_id":"CVE-2026-86415","title":"Connection reuse ignoring the automatic client certificate option on Schannel redirects","description":"libcurl's connection cache match function never considers the automatic client\ncertificate option, so a cached, already authenticated Schannel connection can\nbe handed to a transfer that got redirected to a different origin, even though\nthe code explicitly switched off the auto client cert option for that transfer\nto prevent exactly this.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86415","published":"2026-10-14"},{"cve_id":"CVE-2026-86413","title":"Negotiate credentials sent to redirected origin","description":"When using an *ambient user* in a first transfer doing Negotiate\nauthentication and asked to follow redirects, curl could pass on its\ncredential details to an unrelated second origin when asked to redirect there.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86413","published":"2026-10-14"},{"cve_id":"CVE-2026-86409","title":"Authorization header leak when CURLOPT_AWS_SIGV4 is reset to NULL","description":"Setting `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\nis set next, leaking state information.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-86409","published":"2026-10-14"},{"cve_id":"CVE-2026-82209","title":"Cookie with Domain set to a public suffix saved with wildcard scope","description":"When libpsl support is enabled, libcurl fails to enforce the Public Suffix\nList boundary check when processing a `Set-Cookie` header where the `Domain`\nattribute explicitly matches an origin host that is itself a public suffix\n(e.g., `Domain=co.uk` set by `co.uk`).\n\nInstead of coercing it into a strict host-only cookie, libcurl saves the\ncookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is\ninappropriately included in subsequent outbound requests or HTTP redirects to\narbitrary sibling subdomains under the same public suffix (e.g.,\n`attacker.co.uk`).","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-82209","published":"2026-09-07"},{"cve_id":"CVE-2026-80255","title":"Secure cookie attribute ignored when a tab precedes it in Set-Cookie","description":"A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of\nspace (ascii code 32) immediately before the `Secure` attribute causes curl to\nstore the cookie without its Secure flag. The cookie might then wrongfully be\nsent over plaintext HTTP on subsequent requests to the same host.","severity":"low","cvss_score":3.7,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-201","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-80255","published":"2026-09-07"},{"cve_id":"CVE-2026-94266","title":"Credentials leaked in the URL returned by CURLINFO_EFFECTIVE_URL","description":"libcurl 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.","severity":"low","cvss_score":3.3,"cvss_vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","cwe":"CWE-522","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-94266","published":"2026-10-14"},{"cve_id":"CVE-2026-80229","title":"OpenSSL provider use-after-free","description":"When performing transfers via libcurl’s multi interface, pooled TLS\nconnections can outlive their originating easy handles. In OpenSSL 3 provider\nconfigurations, libcurl attaches an allocated library context to the easy\nhandle's state and passes it to OpenSSL without acquiring an ownership\nreference; destroying the easy handle prematurely frees this context while the\nactive connection retains a dangling pointer, leading to a heap-use-after-free\nupon subsequent I/O or post-handshake operations.","severity":"low","cvss_score":3.1,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","cwe":"CWE-416","product":"curl","reference_count":3,"url":"https://www.cve.org/CVERecord?id=CVE-2026-80229","published":"2026-09-07"}]}