# CVE-2026-33287: LiquidJS has Exponential Memory Amplification through its replace_first Filter $& Pattern

> An attacker can cause denial of service in LiquidJS by exploiting exponential memory amplification in the replace_first filter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-6q5m-63h6-5x4v, MINI-6rxg-4x29-6cxg, MINI-83rx-6hhx-p67q

## What is CVE-2026-33287?

CVE-2026-33287 is a high-severity denial of service vulnerability in harttle liquidjs, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to version 10.25.1, the `replace_first` filter in LiquidJS uses JavaScript's `String.prototype.replace()` which interprets `$&` as a back reference to the matched substring. The filter only charges `memoryLimit` for the input string length, not the amplified output. An attacker can achieve exponential memory amplification (up to 625,000:1) while staying within the `memoryLimit` budget, leading to denial of service. Version 10.25.1 patches the issue.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-33287?

2 open source packages ship an affected version, including liquidjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `liquidjs` | npm | All versions | 10.25.1 |
| `liquidjs` | npm | All versions | 10.25.1 |

Products: Liquidjs Liquidjs.

## How do I fix CVE-2026-33287?

Upgrade liquidjs to 10.25.1 or later.

## Is CVE-2026-33287 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33287 exists.

## Other vulnerabilities in harttle liquidjs

- [CVE-2026-30952](https://insights.sbomify.com/CVE-2026-30952/): liquidjs has a path traversal fallback vulnerability (high 8.7)
- [CVE-2026-35525](https://insights.sbomify.com/CVE-2026-35525/): LiquidJS has a root restriction bypass for partial and layout loading through symlinked templates (high 8.2)
- [CVE-2026-41311](https://insights.sbomify.com/CVE-2026-41311/): LiquidJS is vulnerable to Denial of Service via circular block reference in layout (high 7.5)
- [CVE-2026-33285](https://insights.sbomify.com/CVE-2026-33285/): LiquidJS: memoryLimit Bypass through Negative Range Values Leads to Process Crash (high 7.5)
- [CVE-2026-39859](https://insights.sbomify.com/CVE-2026-39859/): LiquidJS has a renderFile() / parseFile() bypass configured root and allow arbitrary file read (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33287 and fix it if it is affected.

What it is: CVE-2026-33287 is a high-severity denial of service vulnerability in harttle liquidjs, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33287 exists.

Affected packages and fixed versions:
- liquidjs (npm): affected all versions; fixed in 10.25.1
- liquidjs (npm): affected all versions; fixed in 10.25.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33287/ (Markdown: https://insights.sbomify.com/CVE-2026-33287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33287
- OSV: https://osv.dev/vulnerability/CVE-2026-33287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33287/
Summaries are generated and may contain mistakes; the official description above is the record.