CVE-2026-41181: Traefik: Errors middleware forwards Authorization and Cookie headers to separate error page service
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- 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 traefik 2.11.44.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to traefik traefik 2.11.44 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 an HTTP reverse proxy and load balancer. Prior to 2.11.44, 3.6.15, and 3.7.0-rc.3, there is an information disclosure vulnerability in Traefik's errors (custom error pages) middleware. When the backend returns a response matching the configured status range, the middleware forwards the original request's complete header set, including Authorization, Cookie, and other authentication material, to the separate error page service rather than only the minimal context needed to render the error page. This behavior is undocumented: the documentation states only that Host is forwarded by default, so operators are not warned that sensitive credentials are shared across service boundaries. Deployments using the errors middleware with a distinct error page service may inadvertently expose end-user credentials to infrastructure that was not intended to receive them. This vulnerability is fixed in 2.11.44, 3.6.15, and 3.7.0-rc.3.
- Published
- May 15, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-201
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
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
- No public exploit code on record
- 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
- >= 3.7.0-rc.0, < 3.7.0-rc.3, >= 3.0.0-beta1, < 3.6.14, < 2.11.43affected
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.44
- traefik traefik3.0.0 and later · before 3.6.15
- traefik traefik3.7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/traefik/traefik | from 0 | — |
| Go | github.com/traefik/traefik/v2 | before 2.11.44 | 2.11.44 |
| Go | github.com/traefik/traefik/v3 | from 3.7.0-rc.0 · before 3.7.0-rc.3 | 3.7.0-rc.3 |
| Go | github.com/traefik/traefik/v3 | from 3.7.0-rc.1 · before 3.7.0-rc.3 | 3.7.0-rc.3 |
| Go | github.com/traefik/traefik/v3 | before 3.6.15 | 3.6.15 |
| openSUSE:Tumbleweed | traefik | before 3.6.16-1.1 | 3.6.16-1.1 |
| openSUSE:Tumbleweed | traefik2 | before 2.11.45-1.1 | 2.11.45-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-2026-41174Apr 30, 2026 · Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding19Monitor
- ← EarlierCVE-2026-41263Apr 30, 2026 · Traefik: BasicAuth middleware: timing side-channel vulnerability25Monitor
- Later →CVE-2026-44774May 15, 2026 · Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider despite providers.rest.insecure=false25Monitor
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 |
|---|---|---|
| traefik traefik | 2.11.44 · description | Vendor (CNA) |
| Go:github.com/traefik/traefik/v2 | 2.11.44 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v3 | 3.6.15 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v3 | 3.7.0-rc.3 | Package registry (OSV) |
| opensuse:traefik | 3.6.16-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:traefik2 | 2.11.45-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0281 · May 21, 2026(Traefik Proxy Güvenlik Zafiyeti)
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
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)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
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.