LiquidJS: pop filter bypasses memoryLimit accounting that its array-filter siblings enforce

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/ · score source

EPSS

• CVE-2026-55575: 0.49% estimated exploitation activity in the next 30 days; percentile 42.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

pop filter bypasses memoryLimit accounting that its array-filter siblings enforce CWE: CWE-770 (Allocation of Resources Without Limits or Throttling) — sibling class of GHSA-8xx9-69p8-7jp3 and GHSA-2546-xv4c-mc8g, applied to memoryLimit instead of renderLimit Summary The pop array filter at src/filters/array.ts:91-95 allocates a full clone of its input array via [...toArray(v)] but does not call this.context.memoryLimit.use(...) the way every other array-clone filter in the same file does (shift, unshift, compact, concat, reverse, sample, slice, map, sortBy, where, groupby, uniq). This silently disables the memoryLimit budget for {{ hugearray | pop }}, letting a template render allocate an O(N) clone of an attacker-influenced array regardless of how strictly memoryLimit is set. Affected - liquidjs ≥ all versions that ship the current pop filter implementation (verified 10.27.0, HEAD a8fd734b5) - Deployments where any template uses {{ arr | pop }} on an array whose length is…

Published by the source

24 Jul 2026, 14:05 UTC

Last modified by the source

24 Jul 2026, 14:15 UTC

Source last checked

26 Oct 2026, 12:58 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g357-x5c3-c72p

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g357-x5c3-c72p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55575

Advisory: LiquidJS: `pop` filter bypasses `memoryLimit` accounting that its array-filter siblings enforce
IDs: CVE-2026-55575, GHSA-g357-x5c3-c72p
Record: https://patchnext.com/advisories/cve-2026-55575 (revision 3, source checked 26 Oct 2026, 12:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: liquidjs 10.27.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm liquidjs: affected <= 10.27.0; fixed in 10.27.1

## Suggested inspection (read-only)
- `npm ls liquidjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on liquidjs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g357-x5c3-c72p (OSV record GHSA-g357-x5c3-c72p lists affected ranges: npm liquidjs >=0 <10.27.1 (fixed))
- Verified: https://github.com/advisories/GHSA-g357-x5c3-c72p (GitHub-reviewed advisory GHSA-g357-x5c3-c72p lists affected ranges: npm liquidjs >=0 <=10.27.0)

Commands are suggestions: review each one before running it.