LiquidJS: memoryLimit Bypass through Negative Range Values Leads to Process Crash

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-33285: 0.41% estimated exploitation activity in the next 30 days; percentile 35.74 (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.

Summary LiquidJS's memoryLimit security mechanism can be completely bypassed by using reverse range expressions (e.g., (100000000..1)), allowing an attacker to allocate unlimited memory. Combined with a string flattening operation (e.g., replace filter), this causes a V8 Fatal error that crashes the Node.js process, resulting in complete denial of service from a single HTTP request. Details When LiquidJS evaluates a range token (low..high), it calls ctx.memoryLimit.use(high - low + 1) in src/render/expression.ts:70 to account for memory usage. However, for reverse ranges where low high (e.g., (100000000..1)), this computation yields a negative value (1 - 100000000 + 1 = -99999998). The Limiter.use() method in src/util/limiter.ts:11-14 does not validate that the count parameter is non-negative. It simply adds count to this.base, causing the internal counter to go negative. Once the counter is sufficiently negative, subsequent legitimate memory allocations that would normally exceed…

Published by the source

25 Mar 2026, 17:40 UTC

Last modified by the source

30 Mar 2026, 14:05 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9r5m-9576-7f6x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9r5m-9576-7f6x

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

# Patch Next advisory brief: CVE-2026-33285

Advisory: LiquidJS: memoryLimit Bypass through Negative Range Values Leads to Process Crash
IDs: CVE-2026-33285, GHSA-9r5m-9576-7f6x
Record: https://patchnext.com/advisories/cve-2026-33285 (revision 2, source checked 26 Oct 2026, 12:47 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm liquidjs: affected <= 10.24.0

## 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
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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-9r5m-9576-7f6x (OSV record GHSA-9r5m-9576-7f6x lists affected ranges: npm liquidjs >=0 <=10.24.0)
- Verified: https://github.com/advisories/GHSA-9r5m-9576-7f6x (GitHub-reviewed advisory GHSA-9r5m-9576-7f6x lists affected ranges: npm liquidjs >=0 <=10.24.0)

Commands are suggestions: review each one before running it.