# LiquidJS has a memory and render limit bypass via unbounded width padding in \`date\` filter (strftime)

Advisory record · `GHSA-hh27-hf48-9f5q`

- **Identifiers:** `GHSA-hh27-hf48-9f5q` · `CVE-2026-45357`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 27 May 2026
- **Updated:** 28 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 May 2026, 17:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `liquidjs` (npm): affected `<10.26.0`; fixed in `10.26.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> LiquidJS, the npm package liquidjs, is vulnerable in versions before 10.26.0. The date filter's strftime formatting accepts unbounded width specifiers, and padding that output ignores the memoryLimit and renderLimit options, so a single small template can produce megabytes of output and heavy CPU use. An attacker who can influence the date format argument (for example through a context value in a template) can cause denial of service, possibly crashing the host process. Upgrade to liquidjs 10.26.0 or later, which is the listed fixed version.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hh27-hf48-9f5q)

## Sources

- [GitHub Advisory Database: GHSA-hh27-hf48-9f5q](https://github.com/advisories/GHSA-hh27-hf48-9f5q)
- [OSV: GHSA-hh27-hf48-9f5q](https://osv.dev/vulnerability/GHSA-hh27-hf48-9f5q)
- <https://github.com/harttle/liquidjs/security/advisories/GHSA-hh27-hf48-9f5q>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-45357>
- <https://github.com/harttle/liquidjs/commit/3129d46dc95efa357b00e5a57ee1af80a13d72ed>
- <https://github.com/harttle/liquidjs>
- <https://github.com/harttle/liquidjs/blob/v10.26.0/CHANGELOG.md>
- <https://github.com/harttle/liquidjs/releases/tag/v10.26.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hh27-hf48-9f5q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hh27-hf48-9f5q/>. Everything for agents: <https://agentprime.io/llms.txt>.
