Skip to content
Web

CVE-2026-73413

8.7
High
EPSS 0.34%Patch availableAug 13, 2026

Quadratic CPU DoS in Shescape JS via flag-protection loop

common questions

Is CVE-2026-73413 being exploited?

Not confirmed. CVE-2026-73413 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-73413?

CVE-2026-73413 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73413?

Yes. A fix has been recorded for CVE-2026-73413. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73413 affect?

CVE-2026-73413 affects shescape v2.1.11 - v2.1.13, shescape v3.0.0, Node.js/JS apps that include shescape. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73413?

Update to shescape v2.1.14 or v3.0.1 and validate inputs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
shescape v2.1.11 - v2.1.13shescape v3.0.0Node.js/JS apps that include shescape
impact

Attacker-supplied large inputs with many flag fragments cause quadratic CPU usage, leading to CPU exhaustion and denial of service in apps using Shescape.

action required

Patch when possible

affected versions
ericcornelissen shescape
  • affected>= 2.1.11 and < 2.1.14
  • affected>= 3.0.0 and < 3.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free