# CVE-2026-130732: Traefik from 2.11.58 before 2.11.61 Denial of Service via NTLM/Negotiate Headers


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-crjq-37hj-3jf6, GHSA-xv5x-242w-7hf7

## What is CVE-2026-130732?

CVE-2026-130732 is a high-severity vulnerability in traefik, published on 18 Nov 2026. 

### Official description

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.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2026-130732?

2 open source packages ship an affected version, including github.com/traefik/traefik/v2 and github.com/traefik/traefik/v3.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/traefik/traefik/v2` | Go | `pkg:golang/github.com/traefik/traefik/v2` | From 2.11.58 | 2.11.61 |
| `github.com/traefik/traefik/v3` | Go | `pkg:golang/github.com/traefik/traefik/v3` | From 3.7.14 | 3.7.17 |

## How do I fix CVE-2026-130732?

Upgrade github.com/traefik/traefik/v2 to 2.11.61 or later.

## Is CVE-2026-130732 being exploited?

There is no known exploitation of CVE-2026-130732 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130732 and fix it if it is affected.

What it is: CVE-2026-130732 is a high-severity vulnerability in traefik, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130732 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/traefik/traefik/v2 (Go): affected from 2.11.58; fixed in 2.11.61
- github.com/traefik/traefik/v3 (Go): affected from 3.7.14; fixed in 3.7.17

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130732/ (Markdown: https://insights.sbomify.com/CVE-2026-130732/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130732
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130732
- OSV: https://osv.dev/vulnerability/CVE-2026-130732

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130732/
Summaries are generated and may contain mistakes; the official description above is the record.
