CVE-2026-45404: OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access
go.opentelemetry.io/otel/bridge/opentracing introduced an unsynchronized extraBaggageItems map on bridgeSpan. One goroutine can write this map through Span.SetBaggageItem while another goroutine reads and iterates it during correlation baggage propagation, which can trigger Go’s fatal concurrent map access panic and crash the process. The finding is low severity because exploitation requires a specific OpenTracing bridge configuration and concurrent use of the same span.
Introduced in commit: 8cddf30
References
- github.com/advisories/GHSA-42cj-99w8-cp2p
- github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e07ce5ebd1dfe67af42d1e2055d8
- 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/GHSA-42cj-99w8-cp2p
- nvd.nist.gov/vuln/detail/CVE-2026-45404
Code Behaviors & Features
Detect and mitigate CVE-2026-45404 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →