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%, top 47% of all CVEs by exploit prediction. 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
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

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.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

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.
github Patch Available🟡 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 / EcosystemFixed in / 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 rangeFixed inDependents
@opentelemetry/propagator-jaeger—2.9.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 102× 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 134 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 46.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59892?
CVE-2026-59892 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59892, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs