CVE-2026-56018

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

JavaScript::Minifier::XS versions before 0.16 for Perl leak memory on every call to minify(), allowing unbounded memory growth.

In JsMinify (XS.xs) the cleanup frees only the NodeSet structures and never the per-token contents buffers allocated in JsSetNodeContents; JsDiscardNode unlinks nodes without freeing their contents. Each token's contents buffer is therefore leaked on every call, and the two early returns taken when the node list is empty leak the whole NodeSet.

A long-lived process that minifies repeatedly, such as an asset pipeline or a server-side minifier endpoint, grows in memory without bound until it exhausts available memory and is killed, causing denial of service.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
44.9%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
No patch confirmed yet.
generic

Unbound memory growth when calling minify · Issue #10 · bleargh45/JavaScript-Minifier-XS · GitHub

https://github.com/bleargh45/JavaScript-Minifier-XS/issues/10

Vendor Advisories for CVE-2026-56018(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 31× 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:34 UTCEG score recompute
  2. 2026-07-07 00:34 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 12:44 UTCEG score recompute
  6. 2026-07-06 12:44 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:54 UTCEG score recompute
  10. 2026-07-06 00:54 UTCGHSA enrichment
  11. 2026-07-05 13:04 UTCEG score recompute
  12. 2026-07-05 13:04 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 01:15 UTCEG score recompute
  16. 2026-07-05 01:14 UTCGHSA enrichment
  17. 2026-07-04 13:08 UTCEG score recompute
  18. 2026-07-04 13:08 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 01:19 UTCEG score recompute
  22. 2026-07-04 01:19 UTCGHSA enrichment
  23. 2026-07-03 13:30 UTCEG score recompute
  24. 2026-07-03 13:30 UTCGHSA enrichment
  25. 2026-07-03 01:41 UTCEG score recompute 7.50
Show 6 more
  1. 2026-07-03 01:40 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-29 20:57 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  5. 2026-06-29 20:18 UTCEG score recompute
  6. 2026-06-29 20:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56018?
CVE-2026-56018 is a high vulnerability published on June 29, 2026. JavaScript::Minifier::XS versions before 0.16 for Perl leak memory on every call to minify(), allowing unbounded memory growth. In JsMinify (XS.xs) the cleanup frees only the NodeSet structures and never the per-token contents buffers allocated in JsSetNodeContents; JsDiscardNode unlinks nodes…
When was CVE-2026-56018 disclosed?
CVE-2026-56018 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56018 actively exploited?
CVE-2026-56018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56018?
CVE-2026-56018 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-56018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56018, 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

Explore the affected products and dependency analysis for CVE-2026-56018

Explore →

Is Your Infrastructure Affected by CVE-2026-56018?

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