Summary
Traefik's errors middleware forwards Authorization and Cookie headers to separate error page service
Impact
Any deployment that uses the supported errors middleware with a separate error page service can silently copy end-user credentials to that second service whenever the configured error status range is triggered. In practice, this means bearer tokens, session cookies, and other custom authentication headers can be disclosed to infrastructure that was never meant to receive them. If the error service is maintained by a different team, shared across tenants, hosted by a third party, or simply logged more broadly than the primary application service, this expands the exposure of valid credentials and can enable unauthorized API access or account compromise depending on what the leaked tokens authorize.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Frequently Asked Questions
- What is CVE-2026-41181? CVE-2026-41181 is a medium-severity security vulnerability in github.com/traefik/traefik/v2 (go), affecting versions <= 2.11.43. It is fixed in 2.11.44, 3.6.15, 3.7.0-rc.3.
- Which packages are affected by CVE-2026-41181?
github.com/traefik/traefik/v2(go) (versions <= 2.11.43)github.com/traefik/traefik/v3(go) (versions <= 3.6.14)
- Is there a fix for CVE-2026-41181? Yes. CVE-2026-41181 is fixed in 2.11.44, 3.6.15, 3.7.0-rc.3. Upgrade to this version or later.
- Is CVE-2026-41181 exploitable, and should I be worried? Whether CVE-2026-41181 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-41181 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-41181?
- Upgrade
github.com/traefik/traefik/v2to 2.11.44 or later - Upgrade
github.com/traefik/traefik/v3to 3.6.15 or later - Upgrade
github.com/traefik/traefik/v3to 3.7.0-rc.3 or later
- Upgrade