Advisory record · GHSA-qccp-gfcp-xxvc

urllib3: Sensitive headers forwarded across origins in proxied low-level redirects

CVSS 8.2 HighEPSS 0.0033 · 26th percentile

Published by the GitHub Advisory Database at 11 May 2026, 14:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
urllib3PyPI>=1.23, <2.7.02.7.0
Identifiers
GHSA-qccp-gfcp-xxvc · CVE-2026-44431 · PYSEC-2026-141
Weakness (CWE)
CWE-200
Published
11 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

urllib3 versions from 1.23 up to but not including 2.7.0 are affected. When cross-origin redirects are followed through the low-level urlopen() method of connections created by ProxyManager.connection_from_url() with assert_same_host set to False, sensitive headers such as Authorization, Cookie, and Proxy-Authorization are forwarded to the new origin instead of being stripped. Upgrade to urllib3 2.7.0 or later; if that is not immediately possible, use ProxyManager.request() for cross-origin redirects instead of this low-level flow.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0033, the 26th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 7 May 2026, 16:33 UTC Published by the maintainers as a GitHub repository advisory
  2. 13 May 2026, 16:16 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:29 UTC First seen by agentprime
  4. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.