CVE-2026-56017

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2026-40181 (ENISA EUVD) · GHSA-72fp-jmq3-p5xj (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to JavaScript::Minifier::XS version 0.16 or later."

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 29, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
Patch available.

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.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
perl-javascript-minifier-xs—
  • every version up to 0.16-r0: fixed in 0.16-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libjavascript-minifier-xs-perl0.13-1, 0.14-1, 0.15-1, 0.16-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libjavascript-minifier-xs-perl0.15-1, 0.16-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libjavascript-minifier-xs-perl0.15-1, 0.16-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libjavascript-minifier-xs-perl0.15-1
  • every version up to 0.16-1: fixed in 0.16-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 273 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 173 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-25 21:33 UTCEG score recompute
  4. 2026-10-25 21:33 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-25 14:18 UTCEG score recompute
  7. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-24 13:01 UTCEG score recompute
  9. 2026-10-24 13:01 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-18 03:29 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-17 03:07 UTCEG score recompute
  19. 2026-10-17 03:07 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-13 18:54 UTCOSV refresh
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-10-12 15:55 UTCEG score recompute
  2. 2026-10-11 19:38 UTCEG score recompute
  3. 2026-10-11 16:53 UTCEG score recompute
  4. 2026-10-11 14:16 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-23 07:28 UTCEG score recompute
  24. 2026-09-23 07:28 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-18 06:57 UTCEG score recompute
  27. 2026-09-18 06:57 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-14 00:51 UTCEG score recompute
  33. 2026-09-14 00:51 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  34. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-13 09:25 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  36. 2026-09-12 15:14 UTCEG score recompute
  37. 2026-09-12 15:14 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  39. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  41. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-09-06 14:40 UTCEG score recompute
  43. 2026-09-06 14:40 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-08-30 18:30 UTCEG score recompute
  51. 2026-08-30 18:30 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-08-27 22:46 UTCEG score recompute
  55. 2026-08-27 22:46 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  56. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  57. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-08-24 21:46 UTCEG score recompute
  60. 2026-08-24 21:46 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-08-24 06:51 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  62. 2026-08-23 19:40 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-08-23 08:29 UTCEG score recompute
  64. 2026-08-23 08:29 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  66. 2026-08-22 20:50 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-08-22 08:49 UTCEG score recompute
  68. 2026-08-22 08:49 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-08-21 17:21 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  71. 2026-08-21 04:52 UTCEG score recompute
  72. 2026-08-21 04:52 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  73. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  74. 2026-08-20 16:56 UTCGHSA enrichmentGHSA-72fp-jmq3-p5xj · GitHub severity HIGH · GitHub CVSS 7.5
  75. 2026-08-20 05:44 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-56017?
CVE-2026-56017 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-56017 published?
The CVE record for CVE-2026-56017 was published on June 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56017 actively exploited?
CVE-2026-56017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-56017 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to JavaScript::Minifier::XS version 0.16 or later." The vendor advisories EchelonGraph has for CVE-2026-56017 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-56017

Explore →

Is Your Infrastructure Affected by CVE-2026-56017?

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