CVE-2024-45410: HTTP client can remove the X-Forwarded headers in Traefik
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: traefik (Alpine:v3.21) 3.1.3-r0; github.com/traefik/traefik (Go) 2.11.9; github.com/traefik/traefik/v2 (Go) 2.11.9.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.5.
Low priority for now. Upgrade to traefik (Alpine:v3.21) 3.1.3-r0; github.com/traefik/traefik (Go) 2.11.9; github.com/traefik/traefik/v2 (Go) 2.11.9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.5% · 74th percentile
- CWE
- CWE-345
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 9.8
- 2.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| traefik | traefik | cpe:2.3:a:traefik:traefik |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
traefik traefik
- < 2.11.9, >= 3.0.0, < 3.1.3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- traefik traefikbefore 2.11.9
- traefik traefik3.0.0 and later · before 3.1.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | traefik | from 3.0.0 · before 3.1.3-r0 | 3.1.3-r0 |
| Go | github.com/traefik/traefik | from 0 | — |
| Go | github.com/traefik/traefik | before 2.11.9 | 2.11.9 |
| Go | github.com/traefik/traefik/v2 | before 2.11.9 | 2.11.9 |
| Go | github.com/traefik/traefik/v3 | from 3.0.0-beta3 · before 3.1.3 | 3.1.3 |
| openSUSE:Tumbleweed | traefik | before 3.1.4-1.1 | 3.1.4-1.1 |
| openSUSE:Tumbleweed | traefik2 | before 2.11.10-1.1 | 2.11.10-1.1 |
Same product
traefik: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-85595Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth38Monitor
- CVE-2026-88877Traefik v3.7.0 Authentication Bypass via from-to-www-redirect37Monitor
- CVE-2026-88007Traefik HTTP/3 Backend NTLM Connection Reuse36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-28869Apr 12, 2024 · Possible denial of service vulnerability with Content-length header in Traefik30Monitor
- ← EarlierCVE-2024-39321Jul 5, 2024 · Traefik vulnerable to bypassing IP allow-lists via HTTP/3 early data requests in QUIC 0-RTT handshakes30Monitor
- Later →CVE-2024-52003Nov 29, 2024 · X-Forwarded-Prefix Header still allows for Open Redirect in traefik25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:traefik | 3.1.3-r0 · Alpine:v3.21 | Package registry (OSV) |
| Go:github.com/traefik/traefik | 2.11.9 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v2 | 2.11.9 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v3 | 3.1.3 | Package registry (OSV) |
| opensuse:traefik | 3.1.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:traefik2 | 2.11.10-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:5 | 2024-09-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+6 d
- TodayNov 16, 2026+787 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.