# CVE-2023-54365: Traefik - Denial of Service via HTTP/2 Request Handling

> Remote attackers can cause service unavailability in Traefik by exploiting HTTP/2 Rapid Reset attacks to exhaust server resources.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-golang-2023-54365, GHSA-7v4p-328v-8v5g, MINI-7w83-3w4f-6pgc

## What is CVE-2023-54365?

CVE-2023-54365 is a high-severity denial of service vulnerability in Golang Go, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-54365?

5 open source packages ship an affected version, including golang and github.com/traefik/traefik. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.20.10, 1.21.3 |
| `github.com/traefik/traefik` | Go | All versions | 2.10.5 |
| `github.com/traefik/traefik` | Go | All versions | 2.10.5 |
| `github.com/traefik/traefik` | Go | From 3.0.0-beta1 | 3.0.0-beta4 |
| `github.com/traefik/traefik` | Go | From 3.0.0-beta1 | 3.0.0-beta4 |

Products: Golang Go, Redhat Openshift Ai, Traefik Traefik.

## How do I fix CVE-2023-54365?

Upgrade golang to a fixed version for your release line: 1.20.10 or 1.21.3.

## Is CVE-2023-54365 being exploited?

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

## Other vulnerabilities in Golang Go

- [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild)
- [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8)
- [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8)
- [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8)
- [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54365 and fix it if it is affected.

What it is: CVE-2023-54365 is a high-severity denial of service vulnerability in Golang Go, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54365 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.20.10, 1.21.3
- github.com/traefik/traefik (Go): affected all versions; fixed in 2.10.5
- github.com/traefik/traefik (Go): affected all versions; fixed in 2.10.5
- github.com/traefik/traefik (Go): affected from 3.0.0-beta1; fixed in 3.0.0-beta4
- github.com/traefik/traefik (Go): affected from 3.0.0-beta1; fixed in 3.0.0-beta4

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-2023-54365/ (Markdown: https://insights.sbomify.com/CVE-2023-54365/index.md)
```

## Sources

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

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