Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

LiquidJS: Uncontrolled Resource Consumption in join filter allows template authors to bypass memoryLimit and crash the process

CVE-2026-69222GHSA-4r6h-5v86-94p3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (liquidjs 10.27.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm liquidjs

    Affected
    <= 10.27.1
    Fixed in
    10.27.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-69222: 0.63% estimated exploitation activity in the next 30 days; percentile 50.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The join filter (src/filters/array.ts:8-13) charges memoryLimit by array element count, not by the string length it produces, letting a template bypass a configured memoryLimit and allocate strings far past budget — bounded only by V8/process limits, not by memoryLimit. Details concat (array.ts:72) is the enabler: it charges by element count too, but only copies references (cheap for both limiter and heap), so an array's element count can be doubled repeatedly at near-zero real cost. join is where the bug lives — it's the call that actually materializes all referenced content into one string, and its own charge (array.length) doesn't reflect that. Same undercounting class as already-fixed replace (GHSA-mmg9-6m6j-jqqx), replacefirst (GHSA-6q5m-63h6-5x4v), date/strftime (GHSA-hh27-hf48-9f5q) — join wasn't covered. Sibling arraytosentencestring (src/filters/string.ts:210) has the identical defect. PoC Live-reproduced against liquidjs@10.27.1, Node v24.3.0. Verified by…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-4r6h-5v86-94p3

  2. Revision 2 · amended ·

    Amended from osv record GHSA-4r6h-5v86-94p3

  3. Revision 1 · created ·

    Published from ghsa record GHSA-4r6h-5v86-94p3

Agent brief

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

# Patch Next advisory brief: CVE-2026-69222

Advisory: LiquidJS: Uncontrolled Resource Consumption in `join` filter allows template authors to bypass `memoryLimit` and crash the process
IDs: CVE-2026-69222, GHSA-4r6h-5v86-94p3
Record: https://patchnext.com/advisories/cve-2026-69222 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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.2. A vendor fix does not mean a deployment is fixed.

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

## 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://github.com/advisories/GHSA-4r6h-5v86-94p3 (GitHub-reviewed advisory GHSA-4r6h-5v86-94p3 lists affected ranges: npm liquidjs >=0 <=10.27.1)
- Verified: https://osv.dev/vulnerability/GHSA-4r6h-5v86-94p3 (OSV record GHSA-4r6h-5v86-94p3 lists affected ranges: npm liquidjs >=0 <10.27.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…