Home › Guides › Proxy Bugs in HTTP Libraries
✓ checked 16 October 2026, updated 19 October 2026 (Java, Ruby and Go), 23 October 2026 (X-Forwarded-For) · sources: GitHub Advisory Database, NVD CVE API, project release notes, the Go Vulnerability Database, RubyGems, PyPI download data, npm downloads API · method · caveats · download the data
On 15 September 2026, urllib3, the Python library underneath Requests, released version 2.8.0 to fix a bug in how it set up TLS to HTTPS proxies, CVE-2026-97687. urllib3 had 1,323,998,380 downloads from PyPI in September. The same day, the Node.js module proxy-addr, which works out a visitor’s IP address behind reverse proxies for Express, fixed CVE-2026-90711, and Fastify’s copy of it followed hours later. Across the 8 HTTP libraries we checked, we count 26 advisories about proxy handling, 20 of them published in 2026.
proxy-related advisories, 2026 20urllib3 downloads, Sep 2026 1,323,998,380proxy-addr downloads, Sep 2026 446,604,993
Headline findings
- urllib3 could apply settings meant for the destination site to the HTTPS proxy connection. NVD’s description of CVE-2026-97687 says that from 1.26.0 until 2.8.0 “target-server TLS settings are incorrectly applied to the HTTPS proxy connection”, and that setting
cert_reqs=CERT_NONEcould leave later connections reaching the proxy “without certificate verification”. GitHub, as the CVE numbering authority, scores it 7.6 (CVSS 4.0). The release notes warn that configurations relying on the old behaviour may need changes. 2.8.0 also fixed two non-proxy bugs in chunked responses. - A trust-subnet typo in proxy-addr could trust the whole IPv4 internet. NVD’s descriptions of CVE-2026-90711 (proxy-addr 1.1.0 to 2.0.7) and CVE-2026-92395 (@fastify/proxy-addr 3.0.0 to 5.1.0) say a subnet such as
::ffff:10.0.0.0/8“is accepted without error but trusts every IPv4 address on the internet rather than the block it names”, so any client could set the address the app reads from X-Forwarded-For. The fixes are proxy-addr 2.0.8 and @fastify/proxy-addr 5.1.1, both released on 15 September. The CNA score for CVE-2026-90711 is 9.1 (critical, CVSS 3.1). proxy-addr had 446,604,993 npm downloads in September and @fastify/proxy-addr 46,287,628, 9.1 times September 2025. - axios accounts for 13 of the 20 proxy-related advisories in 2026. Most concern its NO_PROXY rules, the list of hosts that should skip the proxy, or Proxy-Authorization headers following redirects. Across all packages, 8 of the 2026 advisories are about NO_PROXY and proxy-bypass rules and 5 about Proxy-Authorization or other headers leaking.
- aiohttp’s 3.14.5 release on 11 October was a bug-fix release, not a security one. Its notes list one WebSocket fix. aiohttp’s most recent proxy-related advisory, CVE-2026-34518, from April, covered Cookie and Proxy-Authorization headers leaking on cross-origin redirects. It had 455,683,674 PyPI downloads in September. httpx has 0 proxy-related advisories in GitHub’s database.
Proxy-related advisories in 2026
Packages and downloads
| Package | Ecosystem | Downloads, Sep 2025 | Downloads, Sep 2026 | Proxy advisories, all time | In 2026 |
|---|---|---|---|---|---|
| urllib3 | Python | 963,059,677 | 1,323,998,380 | 4 | 2 |
| requests | Python | 874,856,371 | 1,208,047,323 | 1 | 0 |
| aiohttp | Python | 249,665,166 | 455,683,674 | 1 | 1 |
| httpx | Python | 283,424,226 | 616,749,620 | 0 | 0 |
| axios | Node.js | 296,429,738 | 486,790,339 | 13 | 13 |
| undici | Node.js | 111,004,708 | 770,210,300 | 5 | 2 |
| proxy-addr | Node.js | 165,861,947 | 446,604,993 | 1 | 1 |
| @fastify/proxy-addr | Node.js | 5,111,024 | 46,287,628 | 1 | 1 |
Every proxy-related advisory
| Published | Package | ID | Summary | Category | GitHub severity |
|---|---|---|---|---|---|
| 5 Oct 2026 | proxy-addr | CVE-2026-90711 | proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet | Client-IP trust (X-Forwarded-For) | Critical |
| 30 Sep 2026 | urllib3 | CVE-2026-97687 | urllib3: HTTPS proxy TLS configuration may be ignored or overridden | Proxy TLS and interception | High |
| 30 Sep 2026 | axios | CVE-2026-101898 | Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls | NO_PROXY and proxy-bypass rules | High |
| 30 Sep 2026 | axios | CVE-2026-101906 | Axios: ReDoS (O(N²)) in shouldBypassProxy host normalization, reachable via untrusted redirect Location | NO_PROXY and proxy-bypass rules | High |
| 30 Sep 2026 | axios | CVE-2026-101899 | Axios: CIDR-form NO_PROXY entries are ignored, causing proxy exclusion bypass for internal IP ranges | NO_PROXY and proxy-bypass rules | Medium |
| 16 Sep 2026 | @fastify/proxy-addr | CVE-2026-92395 | Trust subnet in IPv4-mapped IPv6 notation trusts every IPv4 address (inherited from proxy-addr) | Client-IP trust (X-Forwarded-For) | not rated |
| 20 Jul 2026 | axios | CVE-2026-67315 | Axios: NO_PROXY bypass for 0.0.0.0 local addresses in axios | NO_PROXY and proxy-bypass rules | Medium |
| 20 Jul 2026 | axios | CVE-2026-67320 | Axios Node HTTP adapter can use an inherited proxy after interceptor config cloning | Proxy routing and configuration | High |
| 19 Jun 2026 | undici | CVE-2026-6734 | undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse | Proxy routing and configuration | High |
| 18 Jun 2026 | undici | CVE-2026-9697 | undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent | Proxy TLS and interception | High |
| 4 Jun 2026 | axios | CVE-2026-44486 | Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection | Proxy-Authorization and header leaks | High |
| 4 Jun 2026 | axios | CVE-2026-44487 | Axios: Proxy-Authorization Credential Leak to Origin Server Across HTTP-to-HTTPS Redirect in Axios Node.js HTTP Adapter | Proxy-Authorization and header leaks | High |
| 29 May 2026 | axios | CVE-2026-44489 | Axios has a Patch Bypass: Proxy-Authorization Header Injection via Prototype Pollution — Incomplete Null-Prototype Fix | Proxy-Authorization and header leaks | Low |
| 29 May 2026 | axios | CVE-2026-44492 | axios’s shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718) | NO_PROXY and proxy-bypass rules | High |
| 29 May 2026 | axios | CVE-2026-44494 | axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy` | Proxy TLS and interception | High |
| 11 May 2026 | urllib3 | CVE-2026-44431 | urllib3: Sensitive headers forwarded across origins in proxied low-level redirects | Proxy-Authorization and header leaks | High |
| 5 May 2026 | axios | CVE-2026-42043 | Axios: Incomplete Fix for CVE-2025-62718 — NO_PROXY Protection Bypassed via RFC 1122 Loopback Subnet (127.0.0.0/8) in Axios 1.15.0 | NO_PROXY and proxy-bypass rules | High |
| 5 May 2026 | axios | CVE-2026-42038 | Axios: no_proxy bypass via IP alias allows SSRF | NO_PROXY and proxy-bypass rules | Medium |
| 9 Apr 2026 | axios | CVE-2025-62718 | Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF | NO_PROXY and proxy-bypass rules | Medium |
| 1 Apr 2026 | aiohttp | CVE-2026-34518 | AIOHTTP leaks Cookie and Proxy-Authorization headers on cross-origin redirect | Proxy-Authorization and header leaks | Low |
| 17 Jun 2024 | urllib3 | CVE-2024-37891 | urllib3’s Proxy-Authorization request header isn’t stripped during cross-origin redirects | Proxy-Authorization and header leaks | Medium |
| 4 Apr 2024 | undici | CVE-2024-30260 | Undici’s Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline | Proxy-Authorization and header leaks | Low |
| 16 Feb 2024 | undici | CVE-2024-24758 | Undici proxy-authorization header not cleared on cross-origin redirect in fetch | Proxy-Authorization and header leaks | Low |
| 22 May 2023 | requests | CVE-2023-32681 | Unintended leak of Proxy-Authorization header in requests | Proxy-Authorization and header leaks | Medium |
| 17 Jun 2022 | undici | CVE-2022-32210 | ProxyAgent vulnerable to MITM | Proxy TLS and interception | High |
| 19 Mar 2021 | urllib3 | CVE-2021-28363 | Using default SSLContext for HTTPS requests in an HTTPS proxy doesn’t verify certificate hostname for proxy connection | Proxy TLS and interception | Medium |
Update, 19 October: proxy bugs in Java, Ruby and Go
The same kinds of bug turned up outside Python and Node.js in early October. On 7 Oct, NVD published 5 CVEs for AsyncHttpClient (AHC), an open-source Java library for making HTTP requests whose GitHub repository has 6,396 stars. All 5 were filed by GitHub as the CVE numbering authority, and all concern proxies, tunnels or the credentials a client sends. The next day NVD published one for Mechanize, a Ruby library for automating websites, and one for the HTTP server in Go’s standard library.
What went wrong. 5 of the 7 are about credentials reaching the wrong party: a password resent in reversible form, a site’s login sent in plain text to a proxy, a proxy’s password passed on to the site, or headers re-sent to another host after a redirect or retry. That is the same pattern as the Proxy-Authorization leaks in axios, urllib3 and undici listed above. The most severe, CVE-2026-107282, is scored 9.4 (critical) by GitHub: when AHC retries a request against a different host, the proxy and connection settings can still point at the original host, so its credentials or unencrypted request can go to the new one.
The fixes came first. AHC released 3.0.12, 3.0.13 and 2.16.1 on 9 Aug and 3.0.14 on 24 Sep, weeks before the CVEs appeared in NVD. Mechanize 2.14.1 came out on 23 Aug. Projects still on older versions need to upgrade, now that the CVE entries describe each bug in detail. The Go Vulnerability Database lists the Go bug as fixed in Go 1.26.9 and 1.27.2.
| CVE | Library | In NVD | What goes wrong | Fixed in | Score |
|---|---|---|---|---|---|
| CVE-2026-107282 | AsyncHttpClient | 7 Oct | When a request is retried against a different host, the client can send the original host’s path, credentials or unencrypted request to the new host, including through proxy and CONNECT handling. | 3.0.13, 2.16.1 | 9.4 Critical (GitHub (CNA), CVSS 4.0) |
| CVE-2026-107231 | AsyncHttpClient | 7 Oct | A malicious site or proxy can label a login challenge as Digest but leave out its nonce; the client then falls back to Basic and resends the username and password in reversible form. | 3.0.13, 2.16.1 | 8.7 High (GitHub (CNA), CVSS 4.0) |
| CVE-2026-107232 | AsyncHttpClient | 7 Oct | After a proxy refuses a CONNECT tunnel, the client can still act as if the tunnel exists and write the site’s request, with its Authorization credentials, in plain text to the proxy. | 3.0.12, 2.16.1 | 7.5 High (GitHub (CNA), CVSS 3.1) |
| CVE-2026-107230 | AsyncHttpClient | 7 Oct | Pooled connections that logged in through NTLM, Kerberos or an authenticated SOCKS or CONNECT proxy can be reused for a different user, so a later request runs under the first identity. | 3.0.14 | 7.4 High (GitHub (CNA), CVSS 3.1) |
| CVE-2026-107285 | AsyncHttpClient | 7 Oct | For WebSocket (ws://) requests through a proxy tunnel, the client sends the proxy’s Proxy-Authorization value on to the destination site. | 3.0.12, 2.16.1 | 5.9 Medium (GitHub (CNA), CVSS 3.1) |
| CVE-2026-107715 | Mechanize | 8 Oct | Headers set by the caller, including Proxy-Authorization, Cookie2 and bearer tokens, are sent again to a different host after a redirect. | 2.14.1 | 6.8 Medium (GitHub (CNA), CVSS 3.1) |
| CVE-2026-94439 | Go net/http | 8 Oct | A Go HTTP server that answers a CONNECT request with a 2xx response but doesn’t take over the connection keeps reading it as HTTP, which can allow request smuggling past a proxy that treats it as a tunnel. | 1.26.9, 1.27.2 | 7.5 High (CISA ADP, CVSS 3.1) |
Descriptions are our plain-English summaries of each NVD entry. Scores are those listed in NVD: GitHub’s as numbering authority, and for the Go bug, which Go didn’t score, CISA’s. Mechanize has 42,307,135 downloads on RubyGems in total; Java libraries on Maven Central have no public download counts, so we can’t compare AHC’s reach with the Python and Node.js libraries above.
For CVEs in proxy servers and gateways themselves (HAProxy, Squid, Envoy, frp and others), see the Proxy & AI Gateway CVE Ledger. For download trends in scraping libraries, see the Open-Source Scraping Index, and for exploited bugs in network devices, edge devices in CISA’s KEV catalog. Server-side request forgery, where a server can be made to fetch addresses it shouldn’t, is covered for AI tool servers in MCP servers and SSRF.
Update, 23 October: the X-Forwarded-For bugs
Many apps sit behind a reverse proxy or load balancer, so the address they see on the connection is the proxy’s, not the visitor’s. The proxy passes the visitor’s address on in the X-Forwarded-For header. The trouble is that anyone can send that header. If an app reads it without checking that the request really came through its own proxy, an attacker can claim any address they like. That defeats per-IP rate limits on logins, IP allowlists, “local only” admin pages and the addresses written to audit logs. The proxy-addr bug above is one case of this.
73 CVEs published in NVD so far in 2026 mention X-Forwarded-For, more than in 2023, 2024 and 2025 put together (55: 13, 20 and 22). It isn’t only that more CVEs are published overall. NVD published 49,972 CVEs in 2025 and 88,470 in 2026 up to 23 October, so the share that mention the header went from 0.044% to 0.083%, close to double. Across all years, NVD has 219 matching CVEs.
What the 2026 entries are about. We read all 73 descriptions by hand. In 55, the app trusts an address taken from the header when it shouldn’t, and 27 of those describe getting around a rate limit or login lockout, which allows unlimited password guessing. 9 are about how libraries and proxies pass the header along or parse it, such as dropping repeated values or failing to strip it. 5 are cases where the header’s text ends up in a web page unescaped, and in 4 the header is mentioned only in passing.
Libraries, not just apps. 17 of the 2026 entries are in 13 libraries, frameworks or proxy components that other software is built on, including go-chi (Go), proxy-addr and @fastify/proxy-addr (Node.js), Hono, Spring Cloud Gateway, cpp-httplib and Cloudflare’s pingora-proxy. A bug there affects every app that relies on the library’s idea of the client address. The newest go-chi entry, published on 21 October, is in a helper meant to read the header safely: it skips addresses that belong to trusted proxies but never checks that the connection itself came from one.
The last month. NVD published 20 matching CVEs between 22 September and 23 October, 16 of them about trusting a spoofed address:
| CVE | In NVD | Software | Type |
|---|---|---|---|
| CVE-2026-37604 | 22 Sep | pH7Builder (dating CMS) | Trusts a client-supplied address |
| CVE-2026-92929 | 23 Sep | OpenEye Apex NVR firmware | Trusts a client-supplied address |
| CVE-2026-96651 | 23 Sep | Plex Media Server | Trusts a client-supplied address |
| CVE-2026-84474 | 23 Sep | Ansible Automation Platform | Trusts a client-supplied address |
| CVE-2026-84718 | 23 Sep | Ansible Automation Platform | Trusts a client-supplied address |
| CVE-2026-100390 | 25 Sep | Zoraxy reverse proxy | Trusts a client-supplied address |
| CVE-2026-103592 | 30 Sep | simple-php-router | Trusts a client-supplied address |
| CVE-2026-105741 | 5 Oct | Langflow | Trusts a client-supplied address |
| CVE-2026-107271 | 7 Oct | Gophish | Trusts a client-supplied address |
| CVE-2026-108162 | 10 Oct | Pingvin Share X | Trusts a client-supplied address |
| CVE-2026-108522 | 11 Oct | Sencho | Trusts a client-supplied address |
| CVE-2026-108736 | 11 Oct | Speedtest Tracker | Trusts a client-supplied address |
| CVE-2026-100159 | 16 Oct | Popup Box (WordPress plugin) | Header value injected into a page |
| CVE-2026-111934 | 17 Oct | Coder | Trusts a client-supplied address |
| CVE-2026-111869 | 18 Oct | Plane | Trusts a client-supplied address |
| CVE-2026-105299 | 20 Oct | pingora-proxy | Forwarding-header handling |
| CVE-2026-113703 | 20 Oct | SuggestArr | Trusts a client-supplied address |
| CVE-2026-86146 | 21 Oct | Apache bRPC | Forwarding-header handling |
| CVE-2026-114437 | 21 Oct | go-chi | Trusts a client-supplied address |
| CVE-2026-57210 | 23 Oct | Heimdall | Forwarding-header handling |
Types are our reading of each NVD description. Many of these entries are still listed by NVD as awaiting analysis or deferred, so they don’t all have NVD scores yet.
Method
On 16 October 2026 we pulled every GitHub Advisory Database entry for urllib3, requests, aiohttp, httpx, axios, undici, proxy-addr and @fastify/proxy-addr, and kept those whose summary mentions a proxy, proxied requests, SOCKS or a trust subnet. We dropped withdrawn and duplicate advisories. GitHub’s database had no entry for @fastify/proxy-addr, so we added CVE-2026-92395 from NVD. Categories are ours, assigned from each summary. PyPI downloads for September are from the ClickHouse public copy of PyPI’s download logs; npm downloads are from the npm downloads API. A separate script recomputes every number from the saved responses.
Update, 19 October. We fetched the seven CVEs above from the NVD CVE API on 19 October 2026, the AsyncHttpClient and Mechanize release dates from their GitHub releases, the Go fix versions from the Go Vulnerability Database (GO-2026-6613), and Mechanize’s total downloads from the RubyGems API. They aren’t included in the advisory counts above, which cover the eight Python and Node.js libraries.
Update, 23 October. We searched the NVD CVE API for the keyword X-Forwarded-For on 23 October 2026 and read the 73 entries published in 2026 by hand. Yearly totals come from the same API, queried by publication date. A keyword match means the header appears in the CVE description; NVD counts aren’t grouped by product, so one product can have several entries. These CVEs aren’t included in the advisory counts above.
Caveats
- Advisory counts measure reported bugs. Popular libraries get more scrutiny, so more advisories don’t mean a library is less safe.
- Matching on summaries misses advisories that mention proxies only in the details, and the category labels are a judgement call. The CSV lists every advisory with its summary.
- Downloads include CI systems and mirrors, and count every install, not users. npm’s daily data shows zero downloads on four days in September 2026 for each package, so its September 2026 figures are probably undercounts.
- Severity is GitHub’s rating; NVD and the CVE numbering authorities sometimes score differently.
- This product uses data from the NVD API but is not endorsed or certified by the NVD.
Download the data
- X-Forwarded-For CVEs in 2026 (CSV): all 73 entries, with NVD date and status, our category, the library or framework where there is one, and the NVD description.
- X-Forwarded-For CVEs by year (CSV): matching CVEs and all NVD CVEs by year published, with the share.
- Java, Ruby and Go proxy CVEs (CSV): the seven CVEs in the 19 October update, with NVD dates and status, scores and their source, weakness type, fixed versions, release dates and our summaries.
- Proxy-related advisories (CSV): one row per advisory, with package, IDs, date, severity, summary and category.
- Downloads by package (CSV), September 2025 and September 2026.
Cite as: ProxyPicker, “Proxy Bugs in HTTP Libraries”, 16 October 2026, https://proxypicker.com/http-library-proxy-flaws/. Data: GitHub Advisory Database, NVD, PyPI, npm.
Related: Proxy & AI Gateway CVE Ledger · Open-Source Scraping Index · Edge devices in CISA’s KEV catalog · MCP servers and SSRF.
Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.