CVE
Traefik denial of service via resource leak in NTLM auth handling
Affects Traefik v2.11.58 to v2.11.60 and v3.7.14 to v3.7.16, which allocate a dedicated backend transport. Fixed in 2.11.61 and 3.7.17.
- Exploited
- No known exploitation
- Fix
- Fixed in github.com/traefik/traefik/v2 2.11.61 · github.com/traefik/traefik/v3 3.7.17
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
Traefik from 2.11.58 before 2.11.61 contains a resource leak vulnerability that allows unauthenticated attackers to exhaust resources by sending Authorization headers with NTLM or Negotiate schemes. Attackers can open many short-lived connections that each allocate a dedicated backend transport never released, exhausting memory, file descriptors and backend connections.
Who should check
Teams running Traefik v2.11.58 to v2.11.60 or v3.7.14 to v3.7.16, including those without NTLM or Kerberos backends
“Since v2.11.58 and v3.7.14, Traefik allocates a dedicated backend transport”
cve.now Index
- Exploitation0/40No signal
- Exposure25/25Default setups, CISA rates it automatable
- Reach10/20Affects Go packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: github.com/traefik/traefik/v2 2.11.61 · github.com/traefik/traefik/v3 3.7.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130732 (Traefik from 2.11.58 before 2.11.61 Denial of Service via NTLM/Negotiate Headers), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130732 (entry last updated 2026-11-18):
Affected:
- Go package github.com/traefik/traefik/v2: from 2.11.58, fixed in 2.11.61
- Go package github.com/traefik/traefik/v3: from 3.7.14, fixed in 3.7.17
Fixed versions: 2.11.61, 3.7.17.
Conditions (all must be true for the bug to be hit):
- Traefik v2.11.58 to v2.11.60, or v3.7.14 to v3.7.16 (source: https://github.com/traefik/traefik/security/advisories/GHSA-xv5x-242w-7hf7)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130732 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130732 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/traefik/traefik/security/advisories/GHSA-xv5x-242w-7hf7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130732
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130732"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
From 2.11.58 · fixed in 2.11.61
Fixed in v2.11.61 (released Oct 29, 2026, 20 days before disclosure).
The latest release, v2.11.63, is not affected.
From 3.7.14 · fixed in 3.7.17
Fixed in v3.7.17 (released Oct 29, 2026, 20 days before disclosure).
The latest release, v3.7.19, is not affected.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · traefik/traefik · Advisory GHSA-xv5x-242w-7hf7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130732 |
| Record | NVD · CVE-2026-130732 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130732
Is CVE-2026-130732 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An unauthenticated attacker can exhaust the memory, file descriptors and backend connections of the Traefik process, causing a denial of service. The affected Traefik process can become unavailable.Source: github.com
Which versions are affected by CVE-2026-130732?
github.com/traefik/traefik/v2 (Go): from 2.11.58 before 2.11.61. github.com/traefik/traefik/v3 (Go): from 3.7.14 before 3.7.17.Source: cve.now feed data
Am I affected, and how do I check?
Traefik v2.11.58 to v2.11.60 and v3.7.14 to v3.7.16 are in the affected ranges. Check the installed Traefik release with the version command for your binary or container image and compare it against these ranges.Source: github.com
How do I fix CVE-2026-130732?
Upgrade to Traefik 2.11.61 or later on the 2.11 branch, or to 3.7.17 or later on the 3.7 branch.Source: github.com