Skip to main content
Public proof of conceptFix available

CVE-2024-45410

A public proof of concept exists; no exploitation attested.

  • Published2024-09-19
  • Fixed in3.1.3 · 2.11.9
  • WeaknessCWE-345 · CWE-348

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2024-09-1923:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-45410?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-45410?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP
Traefik
BranchAffectedFixed in
3.x≥ 3.0.0, < 3.1.33.1.3
2.11< 2.11.92.11.9

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • RHSA-2025:8244 Red Hat Product Security40 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.21.0 release

Full record on NVD

Fix

  1. Update Traefik to 3.1.3 · 2.11.9
  2. Vendor fix Red Hat Product Security RHSA-2025:8244 · 40 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2025:8244 · 40 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Advisories and patches

Detection

read 2026-10-23 19:24 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedjphetphoumy/traefik-CVE-2024-45410-poc
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-09-20
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.19.8read 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-345, CWE-348read 2026-10-23
  • NVDweakness (CWE)CWE-345read 2026-10-23
  • FIRST EPSSEPSS score1.5 %2026-10-22
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2024-09-19
Last Modified
2026-06-17
NVD status
Analyzed

Frequently asked questions

What is CVE-2024-45410?

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.

Is CVE-2024-45410 actively exploited?

Active exploitation of CVE-2024-45410 has not been confirmed. Its EPSS score was 1.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-45410?

CVE-2024-45410 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database