Vulnerability in go.opentelemetry.io/otel/bridge/opentracing (CVE-2026-45404)
Summary
Vulnerability in go.opentelemetry.io/otel/bridge/opentracing (CVE-2026-45404). Risk of unauthorized operations or information disclosure. Exploitable via extraBaggageItems. Mitigation: upgrade to 1.45.0 or later.
Original description
The description as published by the source.
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 items without locking. The finding evidence also identifies api/correlation/context.go:160-165 as the path where correlation.MapFromContext invokes the get hook, allowing a read path to run concurrently with baggage writes.
Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can terminate the process with a runtime error such as `fatal error:…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45404 has been found in go.opentelemetry.io/otel/bridge/opentracing.
Attackers can target a specific entry point like extraBaggageItems over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade go.opentelemetry.io/otel/bridge/opentracing to 1.45.0 or later.
If unsure, ask your IT team or search "go.opentelemetry.io/otel/bridge/opentracing CVE-2026-45404" on the vendor's site.
CVE-2026-45404 (go.opentelemetry.io/otel/bridge/opentracing) — CWE-362
Attack surface: extraBaggageItems / bridgeSpan / Span.SetBaggageItem / SetBaggageItem
Patched: 1.45.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in go.opentelemetry.io/otel/bridge/opentracing. Attackers reach the vulnerable code path via extraBaggageItems.
Check the vendor advisory for the affected versions of go.opentelemetry.io/otel/bridge/opentracing. Attack surface: extraBaggageItems / bridgeSpan / Span.SetBaggageItem / SetBaggageItem.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.45.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.opentelemetry.io/otel/bridge/opentracing' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'go.opentelemetry.io/otel/bridge/opentracing' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
go.opentelemetry.io/otel/bridge/opentracingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade go.opentelemetry.io/otel/bridge/opentracing to 1.45.0ステージング環境で 1.45.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。