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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
Which versions are affected by CVE-2026-45357?
2 open source packages ship an affected version, including liquidjs.
| Package | 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.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-45357 being exploited?
There is no known exploitation of CVE-2026-45357 in the wild and no public exploit code.
Sources
Also known as ECHO-ff0b-ce49-520e, GHSA-hh27-hf48-9f5q, MINI-88c9-ghcq-4872, MINI-8crg-r9rv-2rmr, MINI-chx8-c39g-7w5v.