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.
References5
- github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e…
- github.com/open-telemetry/opentelemetry-go/pull/8693
- github.com/open-telemetry/opentelemetry-go/releases/tag/v1.45.0
- github.com/open-telemetry/opentelemetry-go/security/advisories/…
- github.com/open-telemetry/opentelemetry-go/security/advisories/…
Metrics
- CVSS 4.0
-
5.9
MEDIUM
Score source: CNA
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 3 · as of 9 November 2026
- CWE
- CWE-362CWE-667
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.