# CVE-2026-41311: LiquidJS is vulnerable to Denial of Service via circular block reference in layout

> An attacker can cause a Denial of Service by submitting a Liquid template with circular block references, crashing the Node.js process.

- **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:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** CLEANSTART-2026-ZO53086, ECHO-efc0-201a-49b9, GHSA-4rc3-7j7w-m548, MINI-jvxh-m69p-rqvr, MINI-mgm9-xmfh-9j3w, MINI-x34c-36gp-mfxx

## What is CVE-2026-41311?

CVE-2026-41311 is a high-severity denial of service vulnerability in harttle liquidjs, published on 9 May 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.7, a circular block reference in {% layout %} / {% block %} causes an infinite recursive loop, consuming all available memory (~4GB) and crashing the Node.js process with FATAL ERROR: JavaScript heap out of memory. This allows any user who can submit a Liquid template to perform a Denial of Service attack. This issue has been patched in version 10.25.7.

Weakness: CWE-674 (Uncontrolled Recursion)

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

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.7 |
| `liquidjs` | npm | All versions | 10.25.7 |

Products: Liquidjs Liquidjs.

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

Upgrade liquidjs to 10.25.7 or later.

## Is CVE-2026-41311 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41311 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-33285](https://insights.sbomify.com/CVE-2026-33285/): LiquidJS: memoryLimit Bypass through Negative Range Values Leads to Process Crash (high 7.5)
- [CVE-2026-33287](https://insights.sbomify.com/CVE-2026-33287/): LiquidJS has Exponential Memory Amplification through its replace_first Filter $& Pattern (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-41311 and fix it if it is affected.

What it is: CVE-2026-41311 is a high-severity denial of service vulnerability in harttle liquidjs, published on 9 May 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-41311 exists.

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

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-41311/ (Markdown: https://insights.sbomify.com/CVE-2026-41311/index.md)
```

## Sources

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

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