Skip to main content
VulnerabilityPublished Updated

CVE-2026-39858: traefik · Authentication Bypass by Spoofing

Affects traefikSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.8 High · fixed in 3.7.0-rc.2 : patch traefik soon.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Sources agree

CVSS scores by source
CNA (GitHub_M)CVSS 4.07.8
ADP (redhat-SADP)CVSS 3.18.2
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.0-rc.2, 3.6.14, 2.11.43
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade traefik to 3.7.0-rc.2, 3.6.14 or 2.11.43.

Affected software

ProductAffectedFixed in
traefik traefikAffected
  • <2.11.43
  • >=3.0.0-beta1 <3.6.14
  • >=3.7.0-ea.1 <3.7.0-rc.2
Fixed in
  • 2.11.43
  • 3.6.14
  • 3.7.0-rc.2

Description

Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high severity authentication bypass vulnerability in Traefik's ForwardAuth and snippet-based authentication middleware. Traefik's forwarded-header sanitization logic targets only canonical header names (e.g., X-Forwarded-Proto) and does not strip or normalize alias variants that use underscores instead of dashes (e.g., X_Forwarded_Proto). These unsanitized alias headers are forwarded intact to the authentication backend. When the backend normalizes underscore and dash header forms equivalently, an attacker can inject spoofed trust context — such as a trusted scheme or host — through the alias headers and bypass authentication on protected routes without valid credentials. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.

References

Community reviews

Loading reviews…