Answer in brief
CVE-2026-45404 records a Medium severity vulnerability in OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access. The current sources do not mark it as known exploited. The current feed maps open-telemetry/opentelemetry-go (generic), go.opentelemetry.io/otel/bridge/opentracing (go), go.opentelemetry.io/otel/bridge/opentracing (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps open-telemetry/opentelemetry-go (generic), go.opentelemetry.io/otel/bridge/opentracing (go), go.opentelemetry.io/otel/bridge/opentracing (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| open-telemetry/opentelemetry-gogeneric | >= 0.11.0, < 1.45.0 | Not reported |
| go.opentelemetry.io/otel/bridge/opentracinggo | >=0.11.0 <1.45.0 | 1.45.0 |
| go.opentelemetry.io/otel/bridge/opentracinggo | >=0.11.0,<1.45.0 | 1.45.0 |
Published upstream
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.