CVE-2026-55575
Memory-exhaustion DoS in LiquidJS pop filter via cloning large arrays
Is CVE-2026-55575 being exploited?
Not confirmed. CVE-2026-55575 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-55575?
CVE-2026-55575 is rated High with a CVSS score of 8.2. 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-55575?
Yes. A fix has been recorded for CVE-2026-55575. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55575 affect?
CVE-2026-55575 affects LiquidJS (npm) < 10.27.1, Node.js web apps using LiquidJS, Systems rendering untrusted templates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55575?
Upgrade LiquidJS to >=10.27.1; limit template memory and validate inputs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled template input can force an O(N) array clone during render, causing memory exhaustion and denial of service of Node.js processes.
Immediate action required
- affected< 10.27.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.