Skip to content
major vulnerability· requires attention

Traefik is widely used as an edge/load‑balancer in cloud-native infra; an auth bypass can expose many services and is disruptive.

Infrastructure

CVE-2026-85595

9.3
Critical
EPSS 0.41%Patch availableSep 4, 2026

Traefik digestAuth authentication bypass allows unauthorized access to protected routes.

common questions

Is CVE-2026-85595 being exploited?

Not confirmed. CVE-2026-85595 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-85595?

CVE-2026-85595 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-85595?

Yes. A fix has been recorded for CVE-2026-85595. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-85595 affect?

CVE-2026-85595 affects Traefik < v2.11.55, Traefik digestAuth middleware, Traefik-based Ingress controllers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85595?

Upgrade to Traefik v2.11.55+, disable digestAuth or restrict access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Traefik < v2.11.55Traefik digestAuth middlewareTraefik-based Ingress controllers
impact

Remote authentication bypass: attackers can compute valid digest responses with an empty secret to access any digestAuth-protected route.

action required

Immediate action required

affected versions
traefik traefik
  • affected< 2.11.55
  • affected>= 3.0.0 and <= 3.7.10
vendor says fixed in2.11.55

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free