CVE-2026-13311

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.4%, top 72% 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
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.

shell-quote prior to 1.8.5 finalizes parsed tokens in parse() using Array.prototype.concat as a reduce accumulator, which reallocates and copies the entire growing array on every iteration. As a result parse() runs in O(n^2) time relative to the number of input tokens. An attacker who can supply an attacker-controlled string to any code path that calls parse() (no shell metacharacters are required; plain space-separated words suffice) can block the single-threaded Node.js event loop for an extended period with a small input, resulting in a denial of service. There is no code execution or data disclosure; impact is to availability only. Fixed in 1.8.5.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
28.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Quadratic-complexity Denial of Service in `parse()` (CWE-407) · Advisory · ljharb/shell-quote · GitHub

https://github.com/ljharb/shell-quote/security/advisories/GHSA-395f-4hp3-45gv

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-13311?
CVE-2026-13311 is a high vulnerability published on June 25, 2026. shell-quote prior to 1.8.5 finalizes parsed tokens in parse() using Array.prototype.concat as a reduce accumulator, which reallocates and copies the entire growing array on every iteration. As a result parse() runs in O(n^2) time relative to the number of input tokens. An attacker who can supply an…
When was CVE-2026-13311 disclosed?
CVE-2026-13311 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13311 actively exploited?
CVE-2026-13311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13311?
CVE-2026-13311 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-13311?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13311, 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-13311

Explore →

Is Your Infrastructure Affected by CVE-2026-13311?

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

Start Free Scan →Browse All CVEs