Vulnerabilities

Vulnerability · GHSA-xv5x-242w-7hf7

Per-connection backend transport leak from unauthenticated Negotiate/NTLM headers (3.7.14+)

Published Nov 2, 2026 · catalog updated Nov 2, 2026 · Per-connection backend transport leak

Last checked Nov 4, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-xv5x-242w-7hf7. A missing EPSS score is not a low risk. Compare Per-connection backend transport leak with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Per-connection backend transport leak).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
go github.com/traefik/traefik/v2 · go github.com/traefik/traefik/v3

## Summary There is a high severity vulnerability in Traefik's NTLM and Kerberos backend connection handling. Since v2.11.58 and v3.7.14, Traefik allocates a dedicated backend transport to a client connection as soon as a request carries an header with the or scheme, without any valid credential or backend challenge. This transport, its idle backend connection and its goroutines are not released when the client connection closes, and the same pattern exists in FastProxy. An unauthenticated client can therefore open many short-lived connections and exhaust the memory, file descriptors and backend connections of the Traefik process, regardless of whether NTLM or Kerberos backends are configured. Traefik v3.6 and earlier v3 lines, and Traefik v2.11.57 and earlier, are not affected: they only dedicate a transport after the backend answers with a or challenge. ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.61 - https://github.com/traefik/traefik/releases/tag/v3.7.17 ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/traefik/traefik/v2>= v2.11.58, <= v2.11.60
  • go github.com/traefik/traefik/v3>= v3.7.14, <= v3.7.16

How to fix GHSA-xv5x-242w-7hf7

  • Upgrade

    GHSA-xv5x-242w-7hf7 lists a fix boundary at v2.11.60. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in >= v2.11.58 · 3 other packages on the advisory

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-xv5x-242w-7hf7. A missing EPSS score is not a low risk. Compare Per-connection backend transport leak with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= v2.11.58, <= v2.11.60, >= v3.7.14, <= v3.7.16. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-772: Missing Release of Resource after Effective Lifetime. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 2, 2026 · Maintainer security tabs

    Detected

    ## Summary There is a high severity vulnerability in Traefik's NTLM and Kerberos backend connection handling. Since v2.11.58 and v3.7.14, Traefik allocates a dedicated backend transport to a client connection as soon as a request carries an header with the or scheme, without any valid credential or backend challenge. This transport, its idle backend connection and its goroutines are not released w

Sources

  • Maintainer security tabsVendor advisoryGHSA-xv5x-242w-7hf7

    ## Summary There is a high severity vulnerability in Traefik's NTLM and Kerberos backend connection handling. Since v2.11.58 and v3.7.14, Traefik allocates a dedicated backend transport to a client connection as soon as a request carries an header with the or scheme, without any valid credential or backend challenge. This transport, its idle backend connection and its goroutines are not released w

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 4, 2026