critical

CVE-2026-88007

github.com/traefik/traefik: Traefik HTTP/3 Backend NTLM Connection Reuse

Published 10 Sep 2026Modified 14 Sep 2026CWE 287, 863

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

GHSA9.1CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Red Hat9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Trivy's own label is CRITICAL. Rated critical by NVD, GHSA, Red Hat.

Description

Traefik is an open source HTTP reverse proxy and load balancer. From 2.11.0 until 2.11.57 and 3.7.13, the HTTP/3 entrypoint ConnContext does not call service.AddTransportOnContext, so kerberosRoundTripper uses a shared backend transport instead of a transport dedicated to each frontend connection. With HTTP/3 enabled, a backend using connection-bound NTLM or Negotiate authentication, and backend keep-alive, an unrelated client can reuse a backend connection authenticated for a victim, read victim-only data, and act as that victim without the victim credentials. This issue is fixed in 2.11.57 and 3.7.13.

Affected packages and fixed versions

Source	Package	Fixed in
go::GitHub Security Advisory Go	github.com/traefik/traefik/v2, github.com/traefik/traefik/v3	2.11.57 and 1 more
minimos	traefik-3, traefik-fips-3	3.7.13-r0
rapidfort alpine 3.20	traefik	3.7.12-r0
rapidfort alpine 3.21	traefik	3.7.12-r0
rapidfort alpine 3.22	traefik	3.7.12-r0
rapidfort alpine 3.23	traefik	3.7.12-r0
rapidfort alpine 3.24	traefik	3.7.12-r0

Show all 9 entries from 7 sources

Source	Package	Fixed in
go::GitHub Security Advisory Go	github.com/traefik/traefik/v2	2.11.57
go::GitHub Security Advisory Go	github.com/traefik/traefik/v3	3.7.13
minimos	traefik-3	3.7.13-r0
minimos	traefik-fips-3	3.7.13-r0
rapidfort alpine 3.20	traefik	3.7.12-r0
rapidfort alpine 3.21	traefik	3.7.12-r0
rapidfort alpine 3.22	traefik	3.7.12-r0
rapidfort alpine 3.23	traefik	3.7.12-r0
rapidfort alpine 3.24	traefik	3.7.12-r0

References

All 9 references

https://www.cve.org/CVERecord?id=CVE-2026-88007

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs