# CVE-2026-45357: LiquidJS: Memory and render limit bypass via unbounded width padding in `date` filter (strftime)

> Attackers can cause denial of service via memory exhaustion and high CPU usage in LiquidJS by exploiting unbounded width padding in the date 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:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** ECHO-ff0b-ce49-520e, GHSA-hh27-hf48-9f5q, MINI-88c9-ghcq-4872, MINI-8crg-r9rv-2rmr, MINI-chx8-c39g-7w5v

## What is CVE-2026-45357?

CVE-2026-45357 is a high-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 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 written in pure JavaScript. In versions 10.25.7 and below, the date filter's strftime implementation parses width specifiers like %9999999d and forwards the captured width unchecked into pad()/padStart(), leading to memory and render limit bypass. In src/util/underscore.ts, the pad loop performs unbounded string concatenation without consulting the Context's memoryLimit or renderLimit, so a single small template ({{ x | date: '%5000000d' }}) produces megabytes of output and unbounded CPU. The memoryLimit and renderLimit options the docs (src/liquid-options.ts:87-92) advertise as DoS controls — and which the docstring explicitly mentions for strftime — are entirely bypassed. Exploitation can cause large memory allocations, high CPU usage, or OOM crashes per render. This issue has been fixed in version 10.26.0.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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-45357?

Upgrade liquidjs to 10.26.0 or later.

## Is CVE-2026-45357 being exploited?

There is no known exploitation of CVE-2026-45357 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45357 is a high-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45357 in the wild and no public exploit code.

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

## Sources

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

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