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

CVE-2026-88007

Traefik, an open‑source HTTP reverse proxy, had a flaw that let attackers reuse authenticated connections when HTTP/3 was enabled. The bug allowed an attacker to read data meant for another user and impersonate that user without knowing their credentials. The issue is fixed in newer releases.

publishedSep 10, 2026
last modifiedSep 10, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
30th 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 versions 2.11.0 through 2.11.56 and 3.7.0 through 3.7.12. Users running those versions with HTTP/3 enabled and a backend that uses NTLM or Negotiate authentication are affected.

02

Real-world impact

An attacker can hijack a backend connection that has already been authenticated for a victim, read data that only the victim should see, and perform actions as that victim, all without needing the victim’s credentials.

03

Why this severity

The CVSS score of 9.1 reflects that the vulnerability can be exploited remotely over the network, requires no user interaction, and gives an attacker full confidentiality and integrity compromise of victim data. The lack of authentication and the high impact on confidentiality and integrity drive the score to critical.

04

What to do about it

official fix available
recommended steps
  1. 011. Verify your current Traefik version.
  2. 022. Upgrade to Traefik 2.11.57 or later, or 3.7.13 or later.
  3. 033. Restart the Traefik service to apply the update.

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 requirementsPresent
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
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 →