# CVE-2026-44645: LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body

> Attackers can bypass renderLimit DoS protections in LiquidJS using empty loop tags, causing excessive CPU consumption and service unavailability.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** ECHO-3064-ae04-ebb0, GHSA-8xx9-69p8-7jp3, MINI-27x5-pmx5-f9q3, MINI-vxv8-fvcv-9hc4, MINI-w22w-rqp4-8w6v

## What is CVE-2026-44645?

CVE-2026-44645 is a medium-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the renderLimit option can be fully bypassed by a {% for %} (or {% tablerow %}) tag whose body is empty. The renderLimit option is documented in docs/source/tutorials/dos.md as the mechanism that "mitigates this by limiting the time consumed by each render() call." The per-iteration time check is reached only when the body contains at least one template node, so a template such as {%- for i in (1..N) -%}{%- endfor -%} iterates the full collection without ever consulting renderLimit. With a configured renderLimit of 50 ms, a single parseAndRenderSync call has been observed to consume 2.26 seconds (~45× over the limit) and scales linearly with N up to memoryLimit, allowing a low-privileged template author to wedge an event-loop thread for an attacker-chosen duration. Deployments that rely on a finite renderLimit for DoS protection (common in multi-tenant template-authoring environments) can still be forced by a single crafted template to monopolize a Node.js event-loop worker for attacker-controlled time, potentially stalling in-flight requests, with availability impact only. This issue has been fixed in version 10.26.0.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including liquidjs.


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

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

Upgrade liquidjs to 10.26.0 or later.

## Is CVE-2026-44645 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44645 is a medium-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44645 exists.

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

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

## Sources

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

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