curl’s Proxy Security Flaws: 2026 vs the Previous 23 Years

Home › Guides › curl’s Proxy Security Flaws: 2026 vs the Previous 23 Years

✓ checked 27 October 2026 · source: curl project security advisories (curl.se vuln.json and each advisory text) · method · caveats · download the data

The curl project has published 7 security advisories about its proxy handling in 2026, close to the 8 it published in the previous 23 years combined. All 7 concern proxy credentials or proxy authentication, such as passwords being sent to the wrong proxy or reused on the wrong connection. The latest, CVE-2026-86414, was fixed in curl 8.23.0 on 14 October.

Proxy advisories in 2026: 7Proxy advisories 2003–2025: 8Share of 2026 curl advisories: 10.1%

Why this matters

curl and its library libcurl are built into operating systems, programming languages, scrapers and many proxy clients. Any program that sends traffic through an HTTP or SOCKS proxy using libcurl relies on this code to keep proxy passwords and website passwords apart.

curl security advisories about proxy handling, by year published20032003: 1120152015: 2220162016: 1120212021: 1120222022: 2220232023: 1120262026: 77
Number of curl security advisories whose flaw is in curl’s handling of HTTP, HTTPS or SOCKS proxies, by the year the curl project published them. 2026 runs to 27 October. Source: curl project.

What the 2026 advisories describe

  • Credentials crossing between proxies. CVE-2026-7168 and CVE-2026-8927 describe libcurl passing Digest authentication from one proxy to a second proxy when a handle is reused. CVE-2026-6253 describes credentials for one proxy being sent to another when different proxies are set for different URL schemes.
  • Old or wrong credentials reused. CVE-2026-3784 describes curl reusing a proxy connection even when the new request uses different proxy credentials. CVE-2026-9079 describes proxy credentials that were not cleared when an application asked libcurl to clear them. CVE-2026-6429 describes a .netrc password leak that requires an HTTP proxy and a reused connection.
  • A proxy collecting website passwords. In CVE-2026-86414, the curl project says an HTTP proxy could trick libcurl into sending the website’s own credentials (a Basic password or a Negotiate/Kerberos ticket) to the proxy, by answering with a 401 response instead of the expected 407.

The curl project rated 5 of the 2026 flaws Medium and 2 Low. None was rated High, while 4 of the 8 earlier proxy advisories were, including the 2023 SOCKS5 heap overflow (CVE-2023-38545). Most of the 2026 flaws are old: the oldest affected code dates from 2,001.

A bigger share of curl’s advisories

Proxy flaws made up 7 of curl’s 69 security advisories published in 2026 (10.1%), against 8 of 170 from 2003 to 2025 (4.7%). The count of advisories reflects how many flaws were found and reported, so a rise can mean more scrutiny of the code as well as more bugs.

All 15 proxy advisories

CVEPublishedcurl’s titleSeverityFlaw introduced inFixed in
CVE-2003-16052003-08-03Proxy Authentication Header Information LeakageHigh4.5 (1998)7.10.7
CVE-2014-81502015-01-08URL request injectionHigh6.0 (1999)7.40.0
CVE-2015-31532015-04-29sensitive HTTP server headers also sent to proxiesHigh4.0 (1998)7.42.1
CVE-2016-07552016-01-27NTLM credentials not-checked for proxy connection reuseMedium7.10.7 (2003)7.47.0
CVE-2021-228902021-03-31TLS 1.3 session ticket proxy host mix-upLow7.63.0 (2018)7.76.0
CVE-2022-429152022-10-26HTTP proxy double freeMedium7.77.0 (2021)7.86.0
CVE-2022-435522022-12-21HTTP Proxy deny use after freeLow7.16.0 (2006)7.87.0
CVE-2023-385452023-10-11SOCKS5 heap buffer overflowHigh7.69.0 (2020)8.4.0
CVE-2026-37842026-03-11wrong proxy connection reuse with credentialsLow7.7 (2001)8.19.0
CVE-2026-71682026-04-29cross-proxy Digest auth state leakMedium7.12.0 (2004)8.20.0
CVE-2026-64292026-04-29netrc credential leak with reused proxy connectionMedium7.14.0 (2005)8.20.0
CVE-2026-62532026-04-29proxy credentials leak over redirect-to proxyMedium7.14.1 (2005)8.20.0
CVE-2026-90792026-06-24stale proxy password leakMedium8.8.0 (2024)8.21.0
CVE-2026-89272026-06-24env-set cross-proxy Digest auth state leakMedium7.12.0 (2004)8.21.0
CVE-2026-864142026-10-14leaking host credentials to HTTP proxyLow7.10.8 (2003)8.23.0

For proxy flaws in other HTTP libraries, see HTTP library proxy flaws. Vulnerabilities in proxy servers and gateways are tracked in our proxy gateway CVE ledger, and the wider tooling is covered in the open-source scraping index.

Method

We downloaded the curl project’s machine-readable advisory list (curl.se/docs/vuln.json, 239 advisories) on 27 October 2026 and searched each advisory for proxy, SOCKS and tunnel. We then read every match in full and kept only advisories whose flaw is in curl’s own proxy code. We left out CVE-2025-10148, a WebSocket flaw where a proxy cache is the possible victim, not curl’s proxy handling. Severity ratings, versions and dates are the curl project’s own. Release dates come from curl’s release list.

Caveats

  • Classification is our own reading of each advisory. Counting the WebSocket advisory would make the earlier total 9.
  • Advisory counts measure reported and fixed flaws, not how safe a given curl version is. Many of these bugs need unusual settings, such as reusing one handle with different proxies.
  • Programs that bundle an old libcurl stay affected until they update it.

Download the data

Cite as: ProxyPicker, “curl’s Proxy Security Flaws: 2026 vs the Previous 23 Years”, 27 October 2026, https://proxypicker.com/curl-proxy-cves/. Source data: curl project.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.