CVE-2023-54365 — traefik
CVE-2023-54365 is a Uncontrolled Resource Consumption vulnerability in github.com/traefik/traefik. A fix is available for github.com/traefik/traefik — see the affected versions and patch details below.
Traefik - Denial of Service via HTTP/2 Request Handling
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-54365.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/traefik/traefik🐹github.com/traefik/traefikReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Traefik before 2.10.5 and 3.0.0-beta4 is affected by a denial-of-service vulnerability in HTTP/2 request handling inherited from the Go standard library's HTTP/2 implementation (CVE-2023-44487 / CVE-2023-39325, the 'Rapid Reset' technique). A remote attacker can rapidly create and cancel HTTP/2 streams to exhaust server resources and cause service unavailability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/traefik/traefik | all versions | 2.10.5go get github.com/traefik/traefik@v2.10.5 |
| 🐹Go | github.com/traefik/traefik | ≥ 3.0.0-beta1&&< 3.0.0-beta4 | 3.0.0-beta4go get github.com/traefik/traefik@v3.0.0-beta4 |
Affected Products
gogolangopenshift airedhattraefiktraefikDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/traefik/traefik to 2.10.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-54365 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The vulnerability is not caused by Traefik-specific code. Traefik was affected because it depended on a vulnerable version of Go's HTTP/2 implementation from the golang.org/x/net module. The remediation was to update dependencies to a version containing the upstream fix.
The recommended mitigation is to upgrade Traefik to a version that includes the patched HTTP/2 dependency.Source: Red Hat security advisory for CVE-2023-54365 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2023-54365 in your dependencies?
Find it across Go, including transitive dependencies.