Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2026-88877

Traefik, a popular HTTP reverse proxy and load balancer, has a critical flaw in versions 3.7.0 through 3.7.11. When an Ingress uses both an authentication annotation and the from‑to‑www‑redirect annotation, Traefik creates a hidden router that bypasses authentication and other middle‑ware. Updating to version 3.7.12 or later removes the vulnerability.

publishedSep 10, 2026
last modifiedSep 10, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
<1%
37th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Oct 10, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Traefik reverse proxy and load balancer, specifically releases v3.7.0 to v3.7.11 inclusive. Earlier Traefik v2 and v3 releases before v3.7.0 are not affected.

02

Real-world impact

An attacker can craft a request with a non‑numeric or empty port (e.g., 'Host: www.example.com:x') that is routed to the protected backend without any authentication or IP‑allowlisting applied, effectively gaining unauthorized access to services behind Traefik.

03

Why this severity

The CVSS score of 9.3 reflects the vulnerability’s high impact: it allows an attacker to bypass authentication and other security controls (confidentiality, integrity, availability) with no user interaction or special privileges, making it a critical risk for exposed services.

04

What to do about it

official fix available
recommended steps
  1. 011. Upgrade Traefik to version 3.7.12 or later.
  2. 022. Restart the Traefik service to apply the new configuration.

NVD-referenced vendor advisory

05

Timeline

  1. Sep 10, 2026 · 3d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Sep 10, 2026 · 3d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →