Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e07ce5ebd1
- https://github.com/open-telemetry/opentelemetry-go/pull/8693
- https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.45.0
- https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj
- https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj
FAQ
What is CVE-2026-45404?
CVE-2026-45404 is a documented vulnerability. 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 p...
How severe is CVE-2026-45404?
CVSS scoring is not yet available for CVE-2026-45404. Check NVD for updates.
Is there a patch for CVE-2026-45404?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.