CVE-2024-37891

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.4 from GitHub Security Advisory (severity: MODERATE) published 2024-06-17. NVD baseline CVSS 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-1894 (ENISA EUVD) · GHSA-34jh-p97f-mpxf (GitHub Security Advisories)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected. However, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the Proxy-Authorization HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the Proxy-Authorization header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the Proxy-Authorization header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach. We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: 1. Setting the Proxy-Authorization header without using urllib3's built-in proxy support. 2. Not disabling HTTP redirects. 3. Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2. Users unable to upgrade may use the Proxy-Authorization header with urllib3's ProxyManager, disable HTTP redirects using redirects=False when sending requests, or not user the Proxy-Authorization header as mitigations.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.1%
EPSS %ILE
66th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 17, 2024

Last Modified

January 6, 2026

References (5)

Vendor Advisories for CVE-2024-37891(20)

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

Patch Availability(32)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-urllib3-0:1.25.10-7.el8ost2024-11-21redhat
redhatpython3.12-urllib3-0:1.26.18-2.el9_4.12024-11-19redhat
redhatpython3.11-urllib3-0:1.26.12-2.el9_4.12024-11-19redhat
redhatpython3.11-urllib3-0:1.26.12-2.el9_5.12024-11-12redhat
redhatpython3.12-urllib3-0:1.26.18-2.el9_5.12024-11-12redhat
redhatpython-urllib3-0:2.2.3-1.el9pc2024-11-05redhat
redhatpython3.11-urllib3-0:1.26.12-4.el8_102024-11-05redhat
redhatpython3.12-urllib3-0:1.26.19-1.el8_102024-11-05redhat
redhatpython3.11-urllib3-0:1.26.12-1.el8_8.12024-10-14redhat
redhatrhdh/rhdh-hub-rhel9:1.3-1002024-10-02redhat
redhatautomation-controller-0:4.5.12-1.el9ap2024-09-27redhat
redhatpython-urllib3-0:1.26.20-1.el9ap2024-09-18redhat
redhatresource-agents-0:4.9.0-54.el8_10.42024-09-04redhat
redhatresource-agents-0:4.9.0-16.el8_6.132024-09-04redhat
redhatfence-agents-0:4.2.1-129.el8_10.42024-09-04redhat
redhatpython-urllib3-0:1.26.5-3.el9_0.12024-09-04redhat
redhatresource-agents-0:4.1.1-90.el8_4.172024-09-03redhat
redhatpython-urllib3-0:1.26.5-5.el9_4.12024-09-03redhat
redhatpython-urllib3-0:1.26.5-3.el9_2.22024-09-03redhat
redhatfence-agents-0:4.2.1-89.el8_6.132024-08-20redhat
redhatfence-agents-0:4.10.0-20.el9_0.152024-08-20redhat
redhatfence-agents-0:4.10.0-43.el9_2.72024-08-20redhat
redhatpython-urllib3-0:1.24.2-5.el8_8.22024-08-19redhat
redhatcontainer-tools:rhel8-8100020240808093819.afee755d2024-08-13redhat
redhatpython-urllib3-0:1.24.2-8.el8_102024-08-13redhat
redhatpython-urllib3-0:1.24.2-5.el8_6.32024-08-06redhat
redhatfence-agents-0:4.2.1-112.el8_8.72024-07-23redhat
redhatresource-agents-0:4.9.0-40.el8_8.42024-07-23redhat
redhatfence-agents-0:4.2.1-65.el8_4.172024-07-23redhat
redhatfence-agents-0:4.10.0-62.el9_4.42024-07-09redhat
pipurllib3 @ 1.26.19 (fixes < 1.26.19)—ghsa
pipurllib3 @ 2.2.2 (fixes >= 2.0.0, < 2.2.2)—ghsa

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib31.26.5-1~exp1
  • every version up to 1.26.5-1~exp1+deb11u1: fixed in 1.26.5-1~exp1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib31.26.12-1
  • every version up to 1.26.12-1+deb12u1: fixed in 1.26.12-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib3—
  • every version up to 2.2.3-3: fixed in 2.2.3-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib3—
  • every version up to 2.2.3-3: fixed in 2.2.3-3
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
urllib30.2 ... 2.2.1 (92 versions)
  • every version up to 1.26.19: fixed in 1.26.19
  • 2.0.0 up to 2.2.2: fixed in 2.2.2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

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 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 213 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  3. 2026-11-01 08:13 UTCGHSA enrichmentGHSA-34jh-p97f-mpxf · GitHub severity MODERATE · GitHub CVSS 4.4
  4. 2026-11-01 08:13 UTCEG score recompute
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  7. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  11. 2026-10-25 17:07 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  14. 2026-10-24 06:14 UTCEG score recompute
  15. 2026-10-24 06:14 UTCVendor advisory
  16. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  17. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  18. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  19. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  22. 2026-10-18 07:11 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  24. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.1% · 66th percentile
Show 71 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  3. 2026-10-12 17:51 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-11 21:16 UTCEG score recompute
  6. 2026-10-11 16:08 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  9. 2026-10-10 16:25 UTCOSV refresh
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  18. 2026-09-30 19:47 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  22. 2026-09-27 13:44 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  27. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  28. 2026-09-21 20:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  29. 2026-09-21 03:19 UTCOSV refresh
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  31. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  32. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  33. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  34. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  35. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  36. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  37. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  38. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  39. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  40. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  42. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  43. 2026-09-04 13:59 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  46. 2026-09-02 01:12 UTCOSV refresh
  47. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  48. 2026-09-01 04:37 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  49. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  50. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  51. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  52. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  53. 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  54. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  55. 2026-08-24 14:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  56. 2026-08-23 00:18 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  57. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  58. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  59. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  60. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  61. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  62. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  63. 2026-08-16 04:13 UTCOSV refresh
  64. 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  65. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  66. 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  67. 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  68. 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  69. 2026-08-10 23:58 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  70. 2026-08-09 13:45 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  71. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.1% · 63rd percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-37891?
CVE-2024-37891 is a medium-severity vulnerability; its CVE record was published on June 17, 2024. urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected. However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally…
When was the CVE record for CVE-2024-37891 published?
The CVE record for CVE-2024-37891 was published on June 17, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 6, 2026; the record at its source may have been updated since.
Is CVE-2024-37891 actively exploited?
CVE-2024-37891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37891?
CVE-2024-37891 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2024-37891?
A fix for CVE-2024-37891 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-37891 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-37891

Explore →

Is Your Infrastructure Affected by CVE-2024-37891?

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

Book a Demo →Browse All CVEs