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 71% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 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)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
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

Vendor Advisories for CVE-2026-13311(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-1 ... 1.9.0+~1.7.5-1 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-1 ... 1.9.0+~1.7.5-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-shell-quote1.7.4+~1.7.1-1, 1.7.4+~1.7.1-2, 1.8.3+~1.7.5-1, 1.8.4+~1.7.5-11.9.0+~1.7.5-1—
npm(1)
PackageVulnerable rangeFixed inDependents
shell-quote—1.9.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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-08-25 13:48 UTCEPSS rescore
  2. 2026-08-25 00:46 UTCEG score recompute
  3. 2026-08-24 13:17 UTCEG score recompute
  4. 2026-08-23 09:52 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 11:02 UTCEG score recompute
  7. 2026-08-21 23:48 UTCEPSS rescore
  8. 2026-08-21 05:49 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 07:12 UTCEG score recompute
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-19 01:37 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 01:56 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:21 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 04:46 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 05:52 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 18:38 UTCEG score recompute
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 20:02 UTCEG score recompute
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 67 more
  1. 2026-08-11 08:45 UTCEG score recompute
  2. 2026-08-10 23:59 UTCEPSS rescore
  3. 2026-08-09 22:54 UTCEG score recompute
  4. 2026-08-09 13:46 UTCEPSS rescore
  5. 2026-08-09 00:19 UTCEG score recompute
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-08 01:44 UTCEG score recompute
  8. 2026-08-06 15:53 UTCEG score recompute
  9. 2026-08-06 13:46 UTCEPSS rescore
  10. 2026-08-06 04:29 UTCEG score recompute
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 02:31 UTCEG score recompute
  13. 2026-08-04 15:09 UTCEPSS rescore
  14. 2026-08-04 15:08 UTCEG score recompute
  15. 2026-08-04 10:38 UTCEPSS rescore
  16. 2026-08-03 14:00 UTCEG score recompute
  17. 2026-08-03 10:35 UTCEPSS rescore
  18. 2026-08-02 13:02 UTCEG score recompute
  19. 2026-08-02 02:26 UTCEPSS rescore
  20. 2026-08-01 14:27 UTCEG score recompute
  21. 2026-08-01 04:15 UTCEPSS rescore
  22. 2026-07-31 03:22 UTCEG score recompute
  23. 2026-07-30 16:27 UTCEPSS rescore
  24. 2026-07-30 14:26 UTCEG score recompute
  25. 2026-07-30 02:06 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 00:28 UTCEG score recompute
  28. 2026-07-28 15:36 UTCEPSS rescore
  29. 2026-07-27 17:30 UTCEG score recompute
  30. 2026-07-27 14:13 UTCEPSS rescore
  31. 2026-07-26 15:16 UTCEG score recompute
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-25 14:17 UTCEPSS rescore
  35. 2026-07-24 14:17 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:05 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-21 15:24 UTCEPSS rescore
  40. 2026-07-20 17:08 UTCEPSS rescore
  41. 2026-07-19 14:30 UTCEPSS rescore
  42. 2026-07-19 02:28 UTCEPSS rescore
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-16 17:02 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-13 22:30 UTCEPSS rescore
  48. 2026-07-13 06:12 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-09 19:10 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 02:23 UTCEPSS rescore
  54. 2026-07-05 02:30 UTCEPSS rescore
  55. 2026-07-05 02:30 UTCEPSS rescore
  56. 2026-07-04 06:31 UTCEPSS rescore
  57. 2026-07-01 15:06 UTCEPSS rescore
  58. 2026-07-01 15:06 UTCEPSS rescore
  59. 2026-06-30 23:22 UTCEPSS rescore
  60. 2026-06-29 14:06 UTCEPSS rescore
  61. 2026-06-28 14:07 UTCEPSS rescore
  62. 2026-06-28 04:56 UTCEPSS rescore
  63. 2026-06-28 04:56 UTCEPSS rescore
  64. 2026-06-27 03:08 UTCEPSS rescore
  65. 2026-06-25 13:49 UTCEPSS rescore
  66. 2026-06-25 06:06 UTCEG score recompute
  67. 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 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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