CVE-2024-45410

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.5% (74th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-09-19) is not newer than that change (2024-09-25), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-2723 (ENISA EUVD) · GHSA-62c8-mh53-4cqv (GitHub Security Advisories) · GO-2024-3135 (OSV.dev)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Traefik is a golang, Cloud Native Application Proxy. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify these headers. Since the application trusts the value of these headers, security implications might arise, if they can be modified. For HTTP/1.1, however, it was found that some of theses custom headers can indeed be removed and in certain cases manipulated. The attack relies on the HTTP/1.1 behavior, that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been addressed in release versions 2.11.9 and 3.1.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
74th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

September 19, 2024

Last Modified

September 25, 2024

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

HTTP client can remove the X-Forwarded headers · Advisory · traefik/traefik · GitHub

https://github.com/traefik/traefik/security/advisories/GHSA-62c8-mh53-4cqv
GitHub release Patch Available

v3.1.3

Patch available: traefik/traefik v3.1.3

https://github.com/traefik/traefik/releases/tag/v3.1.3
GitHub release Patch Available

v2.11.9

Patch available: traefik/traefik v2.11.9

https://github.com/traefik/traefik/releases/tag/v2.11.9

Vendor Advisories for CVE-2024-45410(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdevspaces/udi-rhel9:3.21-62025-05-28redhat
gogithub.com/traefik/traefik @ 2.11.9 (fixes < 2.11.9)—ghsa
gogithub.com/traefik/traefik/v3 @ 3.1.3 (fixes >= 3.0.0-beta3, < 3.1.3)—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

(7 across 5 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/traefik/traefik—
  • every version up to 2.11.9: fixed in 2.11.9
  • every version on: no fix on record
—
github.com/traefik/traefik/v2—
  • every version up to 2.11.9: fixed in 2.11.9
—
github.com/traefik/traefik/v3—
  • 3.0.0-beta3 up to 3.1.3: fixed in 3.1.3
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
traefik—
  • 3.0.0 up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
traefik—
  • 3.0.0 up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
traefik—
  • 3.0.0 up to 3.1.3-r0: fixed in 3.1.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
traefik—
  • 3.0.0 up to 3.1.3-r0: fixed in 3.1.3-r0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 72× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 292 rows 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. None are among the latest 100 rows. The 192 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCjphetphoumy/traefik-CVE-2024-45410-poc
    Published Sep 26, 2024

    A proof of concept of traefik CVE to understand the impact

    Open source ↗

Frequently asked(5)

What is CVE-2024-45410?
CVE-2024-45410 is a critical-severity vulnerability; its CVE record was published on September 19, 2024. Traefik is a golang, Cloud Native Application Proxy. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify…
When was the CVE record for CVE-2024-45410 published?
The CVE record for CVE-2024-45410 was published on September 19, 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 September 25, 2024; the record at its source may have been updated since.
Is CVE-2024-45410 actively exploited?
CVE-2024-45410 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45410?
CVE-2024-45410 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-45410?
A fix for CVE-2024-45410 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-45410 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-45410

Explore →

Is Your Infrastructure Affected by CVE-2024-45410?

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