CVE-2026-45404

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.9Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
58
EG Risk 58/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 20, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Release v1.45.0/v0.67.0/v0.21.0/v0.0.18

Patch available: open-telemetry/opentelemetry-go v1.45.0

https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.45.0
github_commit

commit 93a693edeed0 (open-telemetry/opentelemetry-go)

Fix landed in open-telemetry/opentelemetry-go commit 93a693edeed0 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e07ce5ebd1dfe67af42d1e2055d8
github_pr

Release v1.45.0

Fix merged in open-telemetry/opentelemetry-go PR #8693 on 2026-08-03 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/pull/8693
github Patch Available🟡 PoC Available

Unsynchronized baggage map can panic under concurrent access · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj-99w8-cp2p

Vendor Advisories for CVE-2026-45404(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.1.0-2 ... 1.46.0-1~exp1 (20 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-1~exp1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-1~exp1 (8 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
go.opentelemetry.io/otel/bridge/opentracing—
  • 0.11.0 up to 1.45.0: fixed in 1.45.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 16:47 UTCEG score recompute
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-02 08:16 UTCEG score recompute
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-10-01 08:11 UTCEG score recompute
  7. 2026-09-30 15:03 UTCEPSS rescore
  8. 2026-09-30 08:14 UTCEG score recompute
  9. 2026-09-29 03:19 UTCEG score recompute
  10. 2026-09-28 03:06 UTCEG score recompute
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-27 03:02 UTCEG score recompute
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-25 00:41 UTCEG score recompute
  15. 2026-09-23 21:25 UTCEG score recompute
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-22 21:29 UTCEG score recompute
  18. 2026-09-21 21:31 UTCEG score recompute
  19. 2026-09-20 21:34 UTCEG score recompute
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-19 21:36 UTCEG score recompute
  22. 2026-09-18 21:39 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-17 21:39 UTCEG score recompute
  25. 2026-09-17 19:31 UTCEPSS rescore
Show 38 more
  1. 2026-09-16 21:42 UTCEG score recompute
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-15 21:13 UTCEG score recompute
  4. 2026-09-13 21:14 UTCEG score recompute
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 21:17 UTCEG score recompute
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 21:20 UTCEG score recompute
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 21:23 UTCEG score recompute
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-09 01:57 UTCEG score recompute
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 20:56 UTCEG score recompute
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-06 21:00 UTCEG score recompute
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-05 21:03 UTCEG score recompute
  19. 2026-09-04 21:07 UTCEG score recompute
  20. 2026-09-02 21:10 UTCEG score recompute
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 19:01 UTCEG score recompute
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-08-31 19:04 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 18:02 UTCEG score recompute
  27. 2026-08-30 01:22 UTCEPSS rescore
  28. 2026-08-29 18:05 UTCEG score recompute
  29. 2026-08-28 21:41 UTCEPSS rescore
  30. 2026-08-27 17:38 UTCEG score recompute
  31. 2026-08-27 17:17 UTCEG score recompute
  32. 2026-08-27 14:25 UTCEPSS rescore
  33. 2026-08-25 22:22 UTCEG score recompute
  34. 2026-08-25 13:49 UTCEPSS rescore
  35. 2026-08-24 22:26 UTCEG score recompute
  36. 2026-08-24 21:33 UTCEG score recompute▲ 5.90
  37. 2026-08-24 21:32 UTCMITRE cvelistV5CVSS v3 → 5.9 · CVSS v4 → 5.9
  38. 2026-08-20 17:42 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

3 shown

Debian:12:golang-opentelemetry-otel

Frequently asked(5)

What is CVE-2026-45404?
CVE-2026-45404 is a medium vulnerability published on August 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…
When was CVE-2026-45404 disclosed?
CVE-2026-45404 was first published on August 20, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45404 actively exploited?
CVE-2026-45404 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45404?
CVE-2026-45404 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45404?
A fix for CVE-2026-45404 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45404 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45404

Explore →

Is Your Infrastructure Affected by CVE-2026-45404?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs