Advisory record · GHSA-42cj-99w8-cp2p

OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access

CVSS 5.9 MediumEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 20 Aug 2026, 17:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
go.opentelemetry.io/otel/bridge/opentracingGo>=0.11.0, <1.45.01.45.0
Identifiers
GHSA-42cj-99w8-cp2p · CVE-2026-45404 · GO-2026-6258
Weakness (CWE)
CWE-362 · CWE-667
Published
20 Aug 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The OpenTelemetry-Go OpenTracing bridge (go.opentelemetry.io/otel/bridge/opentracing) versions from 0.11.0 before 1.45.0 are affected. Concurrent calls to SetBaggageItem and correlation.MapFromContext on the same span can access an unsynchronized map, causing a fatal runtime panic that crashes the process. The attack requires a specific bridge configuration with correlation hooks and concurrent use of one span. Upgrade to version 1.45.0 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.