CVE-2026-45404 OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access
Concurrent access to an unsynchronized map in the OpenTelemetry-Go OpenTracing bridge causes a runtime panic, leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-45404?
CVE-2026-45404 is a medium-severity vulnerability in open-telemetry opentelemetry-go, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0.
Which versions are affected by CVE-2026-45404?
3 open source packages ship an affected version, including go.opentelemetry.io/otel/bridge/opentracing.
| Package | Affected | Fixed in |
|---|---|---|
go.opentelemetry.io/otel/bridge/opentracing Go | From 0.11.0 | 1.45.0 |
go.opentelemetry.io/otel/bridge/opentracing Go | From 0.11.0 | 1.45.0 |
go.opentelemetry.io/otel/bridge/opentracing Go | From 0.11.0 | 1.45.0 |
How do I fix CVE-2026-45404?
Upgrade go.opentelemetry.io/otel/bridge/opentracing to 1.45.0 or later.
Is CVE-2026-45404 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45404 exists.
Sources
Also known as CLEANSTART-2026-FM06572, CLEANSTART-2026-TV94031, DEBIAN-CVE-2026-45404, ECHO-9037-d870-8a06, GHSA-42cj-99w8-cp2p, GO-2026-6258 and 794 more.