Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

Traefik HTTP/3 Backend NTLM Connection Reuse

CVE-2026-88007GHSA-qqjf-53cj-pwvv

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    >= 3.0.0, < 3.7.13
    Fixed in
    3.7.13

  • Go github.com/traefik/traefik/v2

    Affected
    >= 2.11.0, < 2.11.57
    Fixed in
    2.11.57

  • Go github.com/traefik/traefik

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-88007: 0.60% estimated exploitation activity in the next 30 days; percentile 48.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Traefik's HTTP/3 request path did not initialize the connection-scoped backend transport holder that isolates connection-bound NTLM and Negotiate (Kerberos) authentication on the HTTP/1.1 and HTTP/2 paths. The HTTP/3 entrypoint reuses the HTTPS handler chain and reaches the same backend round-tripper, but its ConnContext never called service.AddTransportOnContext, so kerberosRoundTripper fell back to the shared backend transport instead of a per-frontend-connection pool. On a route served over HTTP/3 to a backend that binds identity to a persistent connection via NTLM or Negotiate, an unrelated HTTP/3 client could be assigned a backend connection already authenticated as a victim and inherit that identity, reading victim-only data and performing actions as the victim without presenting the victim's credentials. Affected deployments require HTTP/3 enabled on the entrypoint, a backend using connection-bound NTLM/Negotiate authentication, and backend keep-alive; deployments…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-qqjf-53cj-pwvv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6466

  4. Revision 1 · created ·

    Published from osv record GHSA-qqjf-53cj-pwvv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88007

Advisory: Traefik HTTP/3 Backend NTLM Connection Reuse
IDs: CVE-2026-88007, GHSA-qqjf-53cj-pwvv
Record: https://patchnext.com/advisories/cve-2026-88007 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.7.13; github.com/traefik/traefik/v2 2.11.57. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.0.0, < 3.7.13; fixed in 3.7.13
- Go github.com/traefik/traefik/v2: affected >= 2.11.0, < 2.11.57; fixed in 2.11.57
- Go github.com/traefik/traefik: affected every version

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v3: check the installed version with your package manager.
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.
- Go github.com/traefik/traefik: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qqjf-53cj-pwvv (OSV record GHSA-qqjf-53cj-pwvv lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =2.11.0 <2.11.57 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6466 (OSV record GO-2026-6466 lists affected ranges: Go github.com/traefik/traefik >=0; Go github.com/traefik/traefik/v2 >=2.11.0 =3.0.0 <3.7.13 (fixed))
- Verified: https://github.com/advisories/GHSA-qqjf-53cj-pwvv (GitHub-reviewed advisory GHSA-qqjf-53cj-pwvv lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =2.11.0 <2.11.57)

Commands are suggestions: review each one before running it.

Loading voting…