<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>curl — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/curl" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by curl (curl).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/curl.png</url>
      <title>curl — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:06 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-107929 — local interface connection reuse mixup</title>
      <link>https://vulnogram.org/CVE-2026-107929</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-107929</guid>
      <description>When `CURLOPT_INTERFACE` (or the command line tool&apos;s `--interface` option) is set with one of the documented prefixes (`if!`, `host!`, `ifhost!`), that binding is not part of the connection reuse key, so a later transfer asking for a different source…</description>
      <pubDate>Tue, 20 Oct 2026 20:29:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-107928 — info leak uploading over WebSockets with GnuTLS</title>
      <link>https://vulnogram.org/CVE-2026-107928</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-107928</guid>
      <description>When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when `gnutls_record_send()` returns a number of bytes sent **greater than the number of bytes…</description>
      <pubDate>Tue, 20 Oct 2026 20:28:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94266 — password leak in CURLINFO_EFFECTIVE_URL</title>
      <link>https://vulnogram.org/CVE-2026-94266</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94266</guid>
      <description>libcurl could accidentally return a URL for `curl_easy_getinfo()`&apos;s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.</description>
      <pubDate>Tue, 20 Oct 2026 20:27:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94265 — Authorization: Negotiate sent to foreign origin</title>
      <link>https://vulnogram.org/CVE-2026-94265</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94265</guid>
      <description>When processing an HTTP redirect to a URL containing userinfo (a `username:password` component), curl might erroneously retain and re-transmit the original host&apos;s HTTP Negotiate authentication state. Consequently, a malicious server can trigger a red…</description>
      <pubDate>Tue, 20 Oct 2026 20:26:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92391 — curl_mime_free stack overflow by recursion</title>
      <link>https://vulnogram.org/CVE-2026-92391</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92391</guid>
      <description>A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structu…</description>
      <pubDate>Tue, 20 Oct 2026 20:24:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92390 — -J no-clobber guarantee bypassed with 103 early hints</title>
      <link>https://vulnogram.org/CVE-2026-92390</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92390</guid>
      <description>When invoked with `--remote-header-name` (`-J`), curl fails to preserve its documented anti-clobbering protection if an intermediate 103 Early Hints response precedes the final HTTP response, or if an `ETag` header is processed before `Content-Dispos…</description>
      <pubDate>Tue, 20 Oct 2026 20:23:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92389 — TFTP direction confusion</title>
      <link>https://vulnogram.org/CVE-2026-92389</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92389</guid>
      <description>libcurl&apos;s TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a wa…</description>
      <pubDate>Tue, 20 Oct 2026 20:21:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92388 — FTP wildcard write callback mixup</title>
      <link>https://vulnogram.org/CVE-2026-92388</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92388</guid>
      <description>When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent…</description>
      <pubDate>Tue, 20 Oct 2026 20:20:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92387 — never-ending loop via server response omission</title>
      <link>https://vulnogram.org/CVE-2026-92387</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92387</guid>
      <description>By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can exploit libcurl and completely bypass its configured transfer timeout mechanism, indefinitely blocking all concurrent transfers bound to the same…</description>
      <pubDate>Tue, 20 Oct 2026 20:19:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92386 — server-set cookie aborts cookie jar load</title>
      <link>https://vulnogram.org/CVE-2026-92386</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92386</guid>
      <description>When writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make `curl` write a record that exceeds its line-length parsing limit. Consequently, any subsequent `curl` invocation reading from that same cookie jar using…</description>
      <pubDate>Tue, 20 Oct 2026 20:17:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87866 — wolfSSL public-key pinning bypass</title>
      <link>https://vulnogram.org/CVE-2026-87866</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87866</guid>
      <description>When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl&apos;s subsequent re-parsing of the same certificate - trick…</description>
      <pubDate>Tue, 20 Oct 2026 20:16:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87865 — knownhost callback mismatches key as missing</title>
      <link>https://vulnogram.org/CVE-2026-87865</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87865</guid>
      <description>When libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated initial entry can cause host key validation to report a key *mismatch* as a *missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.</description>
      <pubDate>Tue, 20 Oct 2026 20:15:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87863 — HSTS response erases persisted entries</title>
      <link>https://vulnogram.org/CVE-2026-87863</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87863</guid>
      <description>An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exc…</description>
      <pubDate>Tue, 20 Oct 2026 20:13:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87864 — IMAP APPEND plus CRLF conversion command injection</title>
      <link>https://vulnogram.org/CVE-2026-87864</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87864</guid>
      <description>Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only $N$ bytes for the payload, causing the remaining overflow bytes to be inter…</description>
      <pubDate>Tue, 20 Oct 2026 20:13:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87862 — HSTS cache import drops longer-lived child</title>
      <link>https://vulnogram.org/CVE-2026-87862</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87862</guid>
      <description>Importing a `includeSubDomains` parent HSTS entry before a longer-lived child entry, silently drops the child. Consequently, when the parent expires, the child&apos;s valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than u…</description>
      <pubDate>Tue, 20 Oct 2026 20:10:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-87861 — cross-origin reuse of a Negotiate connection</title>
      <link>https://vulnogram.org/CVE-2026-87861</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-87861</guid>
      <description>When using ambient user credentials, an HTTP request directed to one origin may be dispatched over a connection previously authenticated via Negotiate for a different origin, leaving the request&apos;s intended credentials unused.</description>
      <pubDate>Tue, 20 Oct 2026 20:09:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86415 — auto client cert connection reuse mixup</title>
      <link>https://vulnogram.org/CVE-2026-86415</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86415</guid>
      <description>libcurl&apos;s connection cache match function never considers the automatic client certificate option, so a cached, already authenticated Schannel connection can be handed to a transfer that got redirected to a different origin, even though the code expl…</description>
      <pubDate>Tue, 20 Oct 2026 20:08:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86414 — leaking host credentials to HTTP proxy</title>
      <link>https://vulnogram.org/CVE-2026-86414</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86414</guid>
      <description>An HTTP proxy can trick libcurl into sending the origin&apos;s credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Auth…</description>
      <pubDate>Tue, 20 Oct 2026 20:07:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86413 — Negotiate credentials sent to redirected origin</title>
      <link>https://vulnogram.org/CVE-2026-86413</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86413</guid>
      <description>When using an *ambient user* in a first transfer doing Negotiate authentication and asked to follow redirects, curl could pass on its credential details to an unrelated second origin when asked to redirect there.</description>
      <pubDate>Tue, 20 Oct 2026 20:06:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86412 — server-set cookie erases cookie jar</title>
      <link>https://vulnogram.org/CVE-2026-86412</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86412</guid>
      <description>A remote HTTP server can set a cookie that curl accepts and writes to a Netscape cookie jar but cannot reload. On the next invocation using the same path for `--cookie` and `--cookie-jar`, curl fails before connecting, then the cleanup procedure repl…</description>
      <pubDate>Tue, 20 Oct 2026 20:03:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86411 — FTP connection reuse inherits client-certificate</title>
      <link>https://vulnogram.org/CVE-2026-86411</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86411</guid>
      <description>An `ftp://` transfer configured with `CURLUSESSL_NONE` can reuse a pooled FTP control connection that a previous easy handle upgraded with `STARTTLS` and authenticated using a client certificate. The second handle performs neither a new TLS handshake…</description>
      <pubDate>Tue, 20 Oct 2026 20:02:03 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86410 — redirect to SFTP or SCP bypasses host verification</title>
      <link>https://vulnogram.org/CVE-2026-86410</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86410</guid>
      <description>A flaw in the curl command line tool&apos;s logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect.</description>
      <pubDate>Tue, 20 Oct 2026 19:59:26 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-86409 — stale SigV4 headers sent unintended</title>
      <link>https://vulnogram.org/CVE-2026-86409</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-86409</guid>
      <description>Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, le…</description>
      <pubDate>Tue, 20 Oct 2026 19:57:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-92392 · 8.1 HIGH 🌩️ — HTTP/2 upload Use-After-Free</title>
      <link>https://vulnogram.org/CVE-2026-92392</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-92392</guid>
      <description>During an upload, curl mishandles HTTP/2 `RST_STREAM` received from the server (with reason `HTTP_1_1_REQUIRED` or `REFUSED_STREAM`) leading to a use after free of a `struct Curl_easy` object.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 14 Oct 2026 07:46:15 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-82209 · 8.2 HIGH 🌩️ — domain-scoped PSL domain cookie</title>
      <link>https://vulnogram.org/CVE-2026-82209</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-82209</guid>
      <description>When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` s…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:49:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-82208 · 7.5 HIGH 🌩️ — wolfSSL CA-cache hit overrides callback</title>
      <link>https://vulnogram.org/CVE-2026-82208</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-82208</guid>
      <description>With the wolfSSL backend, when CA caching is enabled and an `CURLOPT_SSL_CTX_FUNCTION` callback replaces the trust store, libcurl can silently reinstall the cached store after the callback returns. A certificate trusted by the cached store but reject…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:49:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-80255 · 7.5 HIGH 🌩️ — secure cookie attribute bypass with tab</title>
      <link>https://vulnogram.org/CVE-2026-80255</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-80255</guid>
      <description>A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintex…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:48:54 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-80231 · 7.5 HIGH 🌩️ — native CA store conn reuse</title>
      <link>https://vulnogram.org/CVE-2026-80231</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-80231</guid>
      <description>A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup for a given hostname even when using a different Native CA Store setting (`CURLSSLOPT_NATIVE_CA`) than when the connection was created.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:48:38 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-80230 · 7.5 HIGH 🌩️ — OpenSSL pinning bypass</title>
      <link>https://vulnogram.org/CVE-2026-80230</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-80230</guid>
      <description>When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a p…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:48:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-80229 · 7.5 HIGH 🌩️ — OpenSSL provider use-after-free</title>
      <link>https://vulnogram.org/CVE-2026-80229</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-80229</guid>
      <description>When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle&apos;s state and passes it t…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:47:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19931 · 9.8 CRITICAL 🌩️ — Negotiate ambient user conn reuse</title>
      <link>https://vulnogram.org/CVE-2026-19931</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19931</guid>
      <description>A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B&apos;s request get sent over user A&apos;s previously authenti…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:47:43 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18924 · 9.1 CRITICAL 🌩️ — HTTP/2 server push UAF</title>
      <link>https://vulnogram.org/CVE-2026-18924</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18924</guid>
      <description>A flaw in libcurl&apos;s handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:47:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-13608 · 7.4 HIGH 🌩️ — OpenLDAP SASL authentication bypass</title>
      <link>https://vulnogram.org/CVE-2026-13608</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-13608</guid>
      <description>A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 06 Sep 2026 17:47:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-9547 · 7.4 HIGH 🌩️ — SSH improper host validation</title>
      <link>https://vulnogram.org/CVE-2026-9547</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-9547</guid>
      <description>When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:18:44 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-9546 · 7.5 HIGH 🌩️ — sending old referer</title>
      <link>https://vulnogram.org/CVE-2026-9546</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-9546</guid>
      <description>A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a res…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:18:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-9545 · 7.5 HIGH 🌩️ — exposing HTTP/3 early data</title>
      <link>https://vulnogram.org/CVE-2026-9545</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-9545</guid>
      <description>In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker&apos;s impostor machine - without a valid certificate. When libcurl returns to…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:17:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-9080 · 7.3 HIGH 🌩️ — UAF after pause in socket callback</title>
      <link>https://vulnogram.org/CVE-2026-9080</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-9080</guid>
      <description>Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer&apos;s memory has been fre…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:17:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-9079 · 9.8 CRITICAL 🌩️ — stale proxy password leak</title>
      <link>https://vulnogram.org/CVE-2026-9079</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-9079</guid>
      <description>libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:16:51 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8932 · 7.5 HIGH 🌩️ — incomplete mTLS config matching in conn reuse</title>
      <link>https://vulnogram.org/CVE-2026-8932</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8932</guid>
      <description>libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:16:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8927 · 9.1 CRITICAL 🌩️ — env-set cross-proxy Digest auth state leak</title>
      <link>https://vulnogram.org/CVE-2026-8927</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8927</guid>
      <description>When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` us…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:16:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8926 · 9.1 CRITICAL 🌩️ — password leak with netrc and user in URL</title>
      <link>https://vulnogram.org/CVE-2026-8926</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8926</guid>
      <description>When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netr…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:15:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8925 · 9.8 CRITICAL 🌩️ — SASL double-free</title>
      <link>https://vulnogram.org/CVE-2026-8925</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8925</guid>
      <description>The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:15:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8924 · 9.1 CRITICAL 🌩️ — trailing dot domain super cookie</title>
      <link>https://vulnogram.org/CVE-2026-8924</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8924</guid>
      <description>A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set &quot;super cookies&quot; that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelate…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:15:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8458 · 6.5 MEDIUM — wrong reuse for different services</title>
      <link>https://vulnogram.org/CVE-2026-8458</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8458</guid>
      <description>libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different &quot;services&quot;. libcurl features a pool of recent connections so that subsequent requests can reuse an e…</description>
      <category>Medium</category>
      <pubDate>Fri, 03 Jul 2026 06:14:42 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8286 · 8.1 HIGH — wrong STARTTLS connection reuse</title>
      <link>https://vulnogram.org/CVE-2026-8286</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8286</guid>
      <description>A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.</description>
      <category>High</category>
      <pubDate>Fri, 03 Jul 2026 06:14:17 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-12064 · 7.5 HIGH 🌩️ — proto-default skips SSH verification</title>
      <link>https://vulnogram.org/CVE-2026-12064</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-12064</guid>
      <description>When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:13:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11856 · 9.8 CRITICAL 🌩️ — cross-origin Digest auth state leak</title>
      <link>https://vulnogram.org/CVE-2026-11856</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11856</guid>
      <description>Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:13:31 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11586 · 7.5 HIGH 🌩️ — WS Auto-PONG memory exhaustion</title>
      <link>https://vulnogram.org/CVE-2026-11586</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11586</guid>
      <description>By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messa…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:13:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11564 · 9.1 CRITICAL 🌩️ — Native CA trust persist</title>
      <link>https://vulnogram.org/CVE-2026-11564</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11564</guid>
      <description>libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the applic…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:12:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11352 · 7.5 HIGH 🌩️ — QUIC zero-length UDP datagrams busy-loop</title>
      <link>https://vulnogram.org/CVE-2026-11352</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11352</guid>
      <description>An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-c…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 03 Jul 2026 06:12:10 GMT</pubDate>
    </item>
  </channel>
</rss>
