CVE-2024-45336

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

Score 6.1 from GitHub Security Advisory published 2025-01-28. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
6.1EG
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: 0.7%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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
0.7%
EPSS %ILE
53rd
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. 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: 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.

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

January 28, 2025

Last Modified

April 15, 2026

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugolang-1.22-src (1.22.2-2~22.04.3) @ jammy2026-05-21ubuntu
redhatrhc-1:0.3.2-1.el10_02025-06-24redhat
redhatyggdrasil-0:0.2.3-3.el9sat2025-05-14redhat
redhatyggdrasil-0:0.4.5-3.el10_02025-05-14redhat
redhatrhc-1:0.2.6-3.el9_62025-05-13redhat
redhatgolang-0:1.23.7-1.el10_02025-05-13redhat
redhatrhacm2/submariner-route-agent-rhel9:v0.18.5-32025-05-12redhat
redhatrhceph/snmp-notifier-rhel9:1.2.1-1002025-05-07redhat
redhatrhacm2/thanos-rhel9:v2.11.7-92025-05-07redhat
redhatopenshift-service-mesh/kiali-rhel8:1.73.20-22025-04-15redhat
redhatgolang-0:1.23.6-2.el9_52025-04-10redhat
redhatgo-toolset:rhel8-8100020250321121115.a3795dee2025-04-10redhat
redhatopentelemetry-collector-0:0.107.0-7.el9_42025-04-03redhat
redhatopentelemetry-collector-0:0.107.0-8.el9_52025-03-27redhat
redhatopenshift-logging/vector-rhel9:v0.37.1-342025-03-26redhat
redhatrhacm2/submariner-rhel9-operator:v0.19.3-32025-03-19redhat
redhatrhosdt/opentelemetry-rhel8-operator:rhosdt-3.52025-03-13redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.24—
  • every version up to 1.24~rc2-1: fixed in 1.24~rc2-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.22.11: fixed in 1.22.11
  • 1.23.0-0 up to 1.23.5: fixed in 1.23.5
  • 1.24.0-0 up to 1.24.0-rc.2: fixed in 1.24.0-rc.2
—

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 95 of 214 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-45336?
CVE-2024-45336 is a medium-severity vulnerability; its CVE record was published on January 28, 2025. The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however,…
When was the CVE record for CVE-2024-45336 published?
The CVE record for CVE-2024-45336 was published on January 28, 2025. 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-45336 actively exploited?
CVE-2024-45336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45336?
CVE-2024-45336 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2024-45336?
A fix for CVE-2024-45336 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-45336 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-45336

Explore →

Is Your Infrastructure Affected by CVE-2024-45336?

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