CVE-2026-59892

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (54th 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. Prior to 2.9.0, @opentelemetry/propagator-jaeger decodes incoming uber-trace-id and uberctx-* HTTP header values with decodeURIComponent() without handling decode errors, allowing an unauthenticated remote attacker to send a malformed percent-encoded value that throws an uncaught URIError and terminates a Node.js process using JaegerPropagator as the active propagator. This issue is fixed in version 2.9.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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
Severity75% × 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.8%
EPSS %ILE
54th
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

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
githubMentions a patch (unverified)🟡 PoC Available

Denial of service in `JaegerPropagator` via unhandled exception on a malformed header · Advisory · open-telemetry/opentelemetry-js · GitHub

https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-45rx-2jwx-cxfr
github_release Patch Available

v2.9.0

Patch available: open-telemetry/opentelemetry-js v2.9.0

https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.9.0
github_commit Patch Available

commit b1c196d49d54 (open-telemetry/opentelemetry-js)

Patch available: open-telemetry/opentelemetry-js experimental/v0.220.0 (contains commit b1c196d49d54)

https://github.com/open-telemetry/opentelemetry-js/commit/b1c196d49d54caae59741cca0a9d57d101d7ea88

Vendor Advisories for CVE-2026-59892(3)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17859728432026-08-10redhat
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@opentelemetry/propagator-jaeger—
  • every version up to 2.9.0: fixed in 2.9.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 42× 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.

Showing the most recent 100 of 199 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-10-01 16:11 UTCEG score recompute
  11. 2026-10-01 16:11 UTCVendor advisory
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-29 15:22 UTCEPSS rescore
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-28 13:22 UTCEG score recompute
  16. 2026-09-28 13:22 UTCVendor advisory
  17. 2026-09-27 13:48 UTCEPSS rescore
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-24 14:04 UTCEPSS rescore
  20. 2026-09-24 11:48 UTCEG score recompute
  21. 2026-09-24 11:48 UTCVendor advisory
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-23 06:10 UTCEG score recompute
  24. 2026-09-23 06:10 UTCVendor advisory
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 75 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:43 UTCEG score recompute
  3. 2026-09-18 05:43 UTCVendor advisory
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-14 11:15 UTCVendor advisory
  9. 2026-09-13 23:49 UTCEG score recompute
  10. 2026-09-13 23:49 UTCVendor advisory
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 08:25 UTCEG score recompute
  13. 2026-09-13 08:25 UTCVendor advisory
  14. 2026-09-12 14:34 UTCVendor advisory
  15. 2026-09-12 03:35 UTCEG score recompute
  16. 2026-09-12 03:35 UTCVendor advisory
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 14:03 UTCEG score recompute
  22. 2026-09-06 14:03 UTCVendor advisory
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 22:48 UTCEG score recompute
  25. 2026-09-05 22:48 UTCVendor advisory
  26. 2026-09-04 05:07 UTCEPSS rescore
  27. 2026-09-02 14:12 UTCEPSS rescore
  28. 2026-09-01 13:54 UTCEPSS rescore
  29. 2026-09-01 04:40 UTCEPSS rescore
  30. 2026-08-30 19:17 UTCEPSS rescore
  31. 2026-08-30 18:32 UTCVendor advisory
  32. 2026-08-30 07:33 UTCEG score recompute
  33. 2026-08-30 07:33 UTCVendor advisory
  34. 2026-08-30 01:22 UTCEPSS rescore
  35. 2026-08-28 21:42 UTCEPSS rescore
  36. 2026-08-27 21:50 UTCEG score recompute
  37. 2026-08-27 21:50 UTCVendor advisory
  38. 2026-08-27 14:25 UTCEPSS rescore
  39. 2026-08-27 01:29 UTCEG score recompute
  40. 2026-08-27 01:29 UTCVendor advisory
  41. 2026-08-26 14:46 UTCEPSS rescore
  42. 2026-08-26 08:24 UTCEG score recompute
  43. 2026-08-26 08:24 UTCVendor advisory
  44. 2026-08-25 13:49 UTCEPSS rescore
  45. 2026-08-25 07:41 UTCVendor advisory
  46. 2026-08-24 20:41 UTCEG score recompute
  47. 2026-08-24 20:41 UTCVendor advisory
  48. 2026-08-24 09:42 UTCEG score recompute
  49. 2026-08-24 09:42 UTCVendor advisory
  50. 2026-08-23 21:56 UTCVendor advisory
  51. 2026-08-23 10:57 UTCEG score recompute
  52. 2026-08-23 10:57 UTCVendor advisory
  53. 2026-08-23 00:19 UTCEPSS rescore
  54. 2026-08-22 23:59 UTCVendor advisory
  55. 2026-08-22 13:00 UTCVendor advisory
  56. 2026-08-22 01:57 UTCEG score recompute
  57. 2026-08-22 01:57 UTCVendor advisory
  58. 2026-08-21 23:49 UTCEPSS rescore
  59. 2026-08-21 14:58 UTCVendor advisory
  60. 2026-08-21 03:59 UTCEG score recompute
  61. 2026-08-21 03:59 UTCVendor advisory
  62. 2026-08-20 22:55 UTCEPSS rescore
  63. 2026-08-20 15:37 UTCVendor advisory
  64. 2026-08-20 01:59 UTCEG score recompute
  65. 2026-08-20 01:59 UTCVendor advisory
  66. 2026-08-19 17:04 UTCEPSS rescore
  67. 2026-08-19 07:44 UTCVendor advisory
  68. 2026-08-18 20:45 UTCEG score recompute
  69. 2026-08-18 20:45 UTCVendor advisory
  70. 2026-08-18 13:48 UTCEPSS rescore
  71. 2026-08-18 02:59 UTCVendor advisory
  72. 2026-08-17 15:59 UTCEG score recompute
  73. 2026-08-17 15:59 UTCVendor advisory
  74. 2026-08-17 13:47 UTCEPSS rescore
  75. 2026-08-17 05:00 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59892?
CVE-2026-59892 is a high vulnerability published on July 8, 2026. OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. Prior to 2.9.0, @opentelemetry/propagator-jaeger decodes incoming uber-trace-id and uberctx-* HTTP header values with decodeURIComponent() without handling decode errors, allowing an unauthenticated remote attacker to send a malformed…
When was CVE-2026-59892 disclosed?
CVE-2026-59892 was first published on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59892 actively exploited?
CVE-2026-59892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59892?
CVE-2026-59892 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59892?
A fix for CVE-2026-59892 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59892 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-59892

Explore →

Is Your Infrastructure Affected by CVE-2026-59892?

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

Book a Demo →Browse All CVEs