cve.bz

CVE-2026-88879 traefik traefik: Authentication Bypass by Spoofing

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in traefik traefik. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/traefik/traefik/v2 2.11.56.

On this page
Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go's lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth's. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to 'keep' for backwards compatibility, it must be explicitly set to 'delete' or 'reject' for the fix to take effect. Unmaintained release lines will not receive a patch.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-290 Authentication Bypass by Spoofing
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-88879 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88879?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88879?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88879 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
traefikbefore 2.11.56
traefikfrom 3.0.0 through 3.7.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rf44-j88r-hh8cGogithub.com/traefik/traefik/v2<2.11.562.11.56
GHSA-rf44-j88r-hh8cGogithub.com/traefik/traefik/v3>=3.0.0 <3.7.123.7.12
GO-2026-6455Gogithub.com/traefik/traefikall versionsno fix published
GO-2026-6455Gogithub.com/traefik/traefik/v2<2.11.562.11.56
GO-2026-6455Gogithub.com/traefik/traefik/v3>=3.0.0 <3.7.123.7.12

Red Hat

Red Hat rates this Critical.

Red Hat's statement

A flaw was found in Traefik's header canonicalization logic, where header names are canonicalized only on dashes. A remote authenticated client can supply dot-form header aliases (e.g., X.Auth.User alongside X-Auth-User) to bypass Traefik middleware assertions. When proxied to backends that collapse non-alphanumeric characters into singular variables (e.g., CGI, WSGI, PHP, NGINX), the backend resolves the attacker-controlled header value over Traefik's asserted identity. This leads to privilege escalation or identity spoofing within the downstream application context.

Red Hat's mitigation

Upgrade to fixed Traefik versions (v2.11.56, v3.7.12, or later) and explicitly configure the entrypoint option aliasHeadersStrategy to 'delete' or 'reject'. Alternatively, configure downstream backend web servers or WSGI/CGI gateways to strip or reject headers containing non-canonical characters before processing.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spaces 3.31devspaces/traefik-rhel9:1792464177Fixed 2026-10-26RHSA-2026:90321
Red Hat OpenShift GitOpsopenshift-gitops-1/argo-rollouts-rhel8Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argo-rollouts-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88879.

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-473 Signature Spoof
  • CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
  • CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON