CVE-2026-54285

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
14.7%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Unbounded memory allocation in W3C Baggage propagation · Advisory · open-telemetry/opentelemetry-js · GitHub

https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-8988-4f7v-96qf

Vendor Advisories for CVE-2026-54285(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@opentelemetry/core—2.8.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 37× 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-07-07 00:15 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 13:00 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 10:48 UTCEG score recompute
  10. 2026-07-03 08:31 UTCEG score recompute
  11. 2026-07-02 06:21 UTCEG score recompute
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 04:10 UTCEG score recompute
  14. 2026-06-30 02:00 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 23:50 UTCEG score recompute
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 21:40 UTCEG score recompute
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 19:28 UTCEG score recompute
  24. 2026-06-25 17:19 UTCEG score recompute
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 12 more
  1. 2026-06-24 15:09 UTCEG score recompute
  2. 2026-06-24 14:05 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 12:59 UTCEG score recompute
  6. 2026-06-22 10:42 UTCEG score recompute
  7. 2026-06-21 08:08 UTCEG score recompute
  8. 2026-06-20 05:55 UTCEG score recompute
  9. 2026-06-19 03:20 UTCEG score recompute
  10. 2026-06-18 01:08 UTCEG score recompute
  11. 2026-06-16 22:58 UTCEG score recompute
  12. 2026-06-15 20:45 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54285?
CVE-2026-54285 is a medium vulnerability published on June 15, 2026. opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were…
When was CVE-2026-54285 disclosed?
CVE-2026-54285 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54285 actively exploited?
CVE-2026-54285 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54285?
CVE-2026-54285 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54285?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54285, 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-54285

Explore →

Is Your Infrastructure Affected by CVE-2026-54285?

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

Start Free Scan →Browse All CVEs