Quick answers
- Is CVE-2026-55575 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55575 being exploited in the wild.
- How severe is CVE-2026-55575?
- High severity, with a CVSS score of 4, published 8 July 2026.
- Which products and versions are affected?
- liquidjs (npm) <= 10.27.0, SEMVER:introduced=0,fixed=10.27.1.
- Is there a fix for CVE-2026-55575?
- Yes. liquidjs (npm): upgrade to 10.27.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55575 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55575?
- Check whether you run liquidjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- liquidjs (npm): upgrade to 10.27.1 or later
npm install liquidjs@10.27.1
Technical details
The 'pop' array filter in 'src/filters/array.ts' fails to call 'this.context.memoryLimit.use()' before performing an O(N) allocation via array cloning. While other array filters like 'shift' or 'slice' correctly account for memory usage against the configured 'memoryLimit', 'pop' bypasses this check entirely. An attacker who can influence the size of an array passed to a template using the 'pop' filter can trigger large allocations that exceed the intended budget. This can lead to process exhaustion and Out-of-Memory (OOM) crashes in Node.js environments. The issue is fixed in version 10.27.1 by adding the missing limit check.
Affected products
- harttle liquidjs <= 10.27.0
Identifiers
- CVE-2026-55575
- GHSA-g357-x5c3-c72p
Timeline
- 2026-07-05: disclosed: Advisory published by maintainer
- 2026-07-08: advisory: NVD publication date
- 2026-07-24: advisory: GitHub Advisory Database reviewed date
- 2026-07-24: patched: Version 10.27.1 released