CVE-2026-44431

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

urllib3 is an HTTP client library for Python. From 1.23 to before 2.7.0, cross-origin redirects followed from the low-level API via ProxyManager.connection_from_url().urlopen(..., assert_same_host=False) still forward these sensitive headers. This vulnerability is fixed in 2.7.0.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
40.7%
KEV
Not listed

Published

May 13, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. Sources: github.
github Patch Available

Sensitive headers forwarded across origins in proxied low-level redirects · Advisory · urllib3/urllib3 · GitHub

https://github.com/urllib3/urllib3/security/advisories/GHSA-qccp-gfcp-xxvc

Vendor Advisories for CVE-2026-44431(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-urllib3 (1.26.5-1~exp1ubuntu0.7) @ jammy2026-06-29ubuntu
redhatrhaiis/model-opt-cuda-rhel9:17823529502026-06-25redhat
redhatrhaiis/vllm-spyre-rhel9:17823529192026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatpython3.14-urllib3-0:2.6.3-2.el9_82026-06-23redhat
redhatpython-urllib3-0:1.26.5-8.el9_82026-06-23redhat
redhatpython3.12-urllib3-0:1.26.19-3.el9_82026-06-23redhat
redhatpython3.14-urllib3-0:2.6.3-2.el10_22026-06-22redhat
redhatpython-urllib3-0:1.26.19-4.el10_22026-06-22redhat
redhatsatellite/iop-vmaas-rhel9:17803929872026-06-16redhat
redhatsatellite/iop-puptoo-rhel9:17797926512026-06-16redhat
redhatsatellite/iop-yuptoo-rhel9:17797929682026-06-16redhat
redhatsatellite/iop-host-inventory-rhel9:17804142372026-06-16redhat
redhatsatellite/iop-insights-engine-rhel9:17797113342026-06-16redhat
redhatansible-automation-platform-27/hub-rhel9:17811028162026-06-15redhat
redhatjaeger-main-2.19.0-1.hum12026-06-10redhat
redhatrhaii/model-opt-cuda-rhel9:17803569412026-06-08redhat
redhatrhtas/model-transparency-rhel9:17809148862026-06-08redhat
redhatrhaii/vllm-cuda-rhel9:17803569142026-06-08redhat
redhatrhaii/vllm-cpu-rhel9:17803568112026-06-08redhat
redhatrhaii/vllm-spyre-rhel9:17803569042026-06-08redhat
redhatpython-urllib3-main-2.7.0-3.hum12026-06-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
urllib31.23 ... 2.6.3 (62 versions)2.7.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 110 total refreshes for this CVE.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-29 22:26 UTCEG score recompute
  8. 2026-06-29 22:26 UTCVendor advisory
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 23:32 UTCEG score recompute
  13. 2026-06-27 23:32 UTCVendor advisory
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-26 20:32 UTCEG score recompute
  16. 2026-06-26 20:32 UTCVendor advisory
  17. 2026-06-25 19:40 UTCEG score recompute
  18. 2026-06-25 19:40 UTCVendor advisory
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-17 21:44 UTCEG score recompute
  7. 2026-06-17 21:44 UTCVendor advisory
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-16 22:44 UTCEG score recompute
  10. 2026-06-16 22:44 UTCVendor advisory
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-16 00:55 UTCEG score recompute
  13. 2026-06-16 00:55 UTCVendor advisory
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-14 21:34 UTCEG score recompute
  16. 2026-06-14 21:34 UTCVendor advisory
  17. 2026-06-13 23:46 UTCEG score recompute
  18. 2026-06-13 23:46 UTCVendor advisory
  19. 2026-06-13 23:00 UTCEPSS rescore
  20. 2026-06-13 01:31 UTCEG score recompute
  21. 2026-06-13 01:31 UTCVendor advisory
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 03:44 UTCEG score recompute
  25. 2026-06-12 03:44 UTCVendor advisory
  26. 2026-06-11 14:00 UTCEPSS rescore
  27. 2026-06-11 05:55 UTCEG score recompute
  28. 2026-06-11 05:55 UTCVendor advisory
  29. 2026-06-10 22:18 UTCEPSS rescore
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 08:08 UTCEG score recompute
  33. 2026-06-10 08:08 UTCVendor advisory
  34. 2026-06-09 10:20 UTCEG score recompute
  35. 2026-06-09 10:20 UTCVendor advisory
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 12:32 UTCEG score recompute
  39. 2026-06-08 12:32 UTCVendor advisory
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 14:45 UTCEG score recompute
  43. 2026-06-07 14:45 UTCVendor advisory
  44. 2026-06-06 16:57 UTCEG score recompute
  45. 2026-06-06 16:57 UTCVendor advisory
  46. 2026-06-06 13:47 UTCEPSS rescore
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-05 22:47 UTCEPSS rescore
  49. 2026-06-05 19:09 UTCEG score recompute
  50. 2026-06-05 19:09 UTCVendor advisory
  51. 2026-06-05 06:10 UTCEPSS rescore
  52. 2026-06-05 06:10 UTCEPSS rescore
  53. 2026-06-04 21:21 UTCEG score recompute
  54. 2026-06-04 21:21 UTCVendor advisory
  55. 2026-06-04 13:12 UTCEPSS rescore
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-03 23:33 UTCEG score recompute
  58. 2026-06-03 23:33 UTCVendor advisory
  59. 2026-06-03 01:45 UTCEG score recompute
  60. 2026-06-03 01:45 UTCVendor advisory
  61. 2026-06-02 20:13 UTCEPSS rescore
  62. 2026-06-02 03:57 UTCEG score recompute
  63. 2026-06-02 03:57 UTCVendor advisory
  64. 2026-06-01 13:52 UTCEPSS rescore
  65. 2026-06-01 13:52 UTCEPSS rescore
  66. 2026-06-01 06:05 UTCEG score recompute
  67. 2026-06-01 06:05 UTCVendor advisory
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44431?
CVE-2026-44431 is a medium vulnerability published on May 13, 2026. urllib3 is an HTTP client library for Python. From 1.23 to before 2.7.0, cross-origin redirects followed from the low-level API via ProxyManager.connectionfromurl().urlopen(..., assertsamehost=False) still forward these sensitive headers. This vulnerability is fixed in 2.7.0.
When was CVE-2026-44431 disclosed?
CVE-2026-44431 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44431 actively exploited?
CVE-2026-44431 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44431?
CVE-2026-44431 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44431?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44431, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44431

Explore →

Is Your Infrastructure Affected by CVE-2026-44431?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs