CVE-2026-56017

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: 0%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 crash with a NULL pointer dereference when the first meaningful token of the input is a slash.

The regexp versus division disambiguator in JsTokenizeString (XS.xs) inspects the previous token's last byte to choose between a regexp literal and a division operator. When a slash is the first meaningful token, with the start of input or only whitespace and comments before it, there is no valid preceding token: the walk back over whitespace and comment nodes runs off the head of the node list to NULL, and the byte lookup reads through a NULL contents pointer at an underflowed length index. The following identifier check dereferences the same NULL pointer.

The crash is reachable through the public minify() API, so input as small as a single slash byte crashes the calling process. A service that minifies untrusted or third-party JavaScript can be crashed by a remote request, causing denial of service.

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

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (1)

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

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

Frequently asked(5)

What is CVE-2026-56017?
CVE-2026-56017 is a high vulnerability published on June 29, 2026. JavaScript::Minifier::XS versions before 0.16 for Perl crash with a NULL pointer dereference when the first meaningful token of the input is a slash. The regexp versus division disambiguator in JsTokenizeString (XS.xs) inspects the previous token's last byte to choose between a regexp literal and a…
When was CVE-2026-56017 disclosed?
CVE-2026-56017 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-56017 actively exploited?
CVE-2026-56017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56017?
CVE-2026-56017 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-56017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56017, 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-56017

Explore →

Is Your Infrastructure Affected by CVE-2026-56017?

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