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
Trending — 4 sources updated this weekElevated

Also known asEUVD-2024-2723 (ENISA EUVD) · GHSA-62c8-mh53-4cqv (GitHub Security Advisories)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-01). 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(1)

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

(3 across 1 ecosystem)
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
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 77× 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 98 of 245 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

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.

Book a Demo →Browse All CVEs