# CVE-2026-69222: LiquidJS: Uncontrolled Resource Consumption in `join` filter allows template authors to bypass `memoryLimit` and crash the 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
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-4r6h-5v86-94p3, MINI-8wqf-h6r6-7c6q, MINI-9ch6-mxwr-p3hp, MINI-px56-6rrg-f85w

## What is CVE-2026-69222?

CVE-2026-69222 is a high-severity vulnerability in harttle liquidjs, published on 19 Aug 2026. 

### Official description

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.2, the join filter in src/filters/array.ts computes complexity from array.length and separator length instead of the total string length produced by array.join(sep). The concat filter can cheaply double arrays of references, after which join materializes the referenced content while charging only for element count, allowing a template to exceed a configured memoryLimit by a large factor. The sibling array_to_sentence_string filter in src/filters/string.ts has the same accounting defect, and a crafted template can allocate toward V8's string or process memory limit and crash the process. This issue is fixed in version 10.27.2.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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


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

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

Upgrade liquidjs to 10.27.2 or later.

## Is CVE-2026-69222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69222 is a high-severity vulnerability in harttle liquidjs, published on 19 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-69222 in the wild and no public exploit code.

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

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

## Sources

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

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