Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

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

CVE-2026-45404GHSA-42cj-99w8-cp2p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (go.opentelemetry.io/otel/bridge/opentracing 1.45.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.9 · 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 · score source
EPSS
  • CVE-2026-45404: 0.14% estimated exploitation activity in the next 30 days; percentile 3.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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 Details bridge/opentracing/bridge.go:80-85 adds extraBaggageItems map[string]string to bridgeSpan without a mutex or other synchronization primitive. bridge/opentracing/bridge.go:219-234 shows SetBaggageItem calling updateOtelContext, which lazily creates the map and writes s.extraBaggageItems[restrictedKey] = value without locking. bridge/opentracing/bridge.go:359-377 shows correlationGetHook reading bSpan.extraBaggageItems, checking len(items), and iterating for k, v := range…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-42cj-99w8-cp2p

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6258

  4. Revision 1 · created ·

    Published from osv record GHSA-42cj-99w8-cp2p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45404

Advisory: OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access
IDs: CVE-2026-45404, GHSA-42cj-99w8-cp2p
Record: https://patchnext.com/advisories/cve-2026-45404 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.opentelemetry.io/otel/bridge/opentracing 1.45.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/otel/bridge/opentracing: affected >= 0.11.0, < 1.45.0; fixed in 1.45.0

## Suggested inspection (read-only)
- Go go.opentelemetry.io/otel/bridge/opentracing: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.opentelemetry.io/otel/bridge/opentracing.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-42cj-99w8-cp2p (OSV record GHSA-42cj-99w8-cp2p lists affected ranges: Go go.opentelemetry.io/otel/bridge/opentracing >=0.11.0 <1.45.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6258 (OSV record GO-2026-6258 lists affected ranges: Go go.opentelemetry.io/otel/bridge/opentracing >=0.11.0 <1.45.0 (fixed))
- Verified: https://github.com/advisories/GHSA-42cj-99w8-cp2p (GitHub-reviewed advisory GHSA-42cj-99w8-cp2p lists affected ranges: Go go.opentelemetry.io/otel/bridge/opentracing >=0.11.0 <1.45.0)

Commands are suggestions: review each one before running it.

Loading voting…