# CVE-2026-44644: LiquidJS's strip_html filter bypass via newline characters in HTML tags enables XSS

> Attacker can bypass HTML sanitization in LiquidJS using newlines in tags, leading to XSS in applications relying on the strip_html filter.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** ECHO-e1c4-2b6b-9317, GHSA-2qv6-9wx5-cwv4, MINI-3v5x-6mm2-8mxc, MINI-f4cm-9gc2-qh32, MINI-jfpr-qp67-6848

## What is CVE-2026-44644?

CVE-2026-44644 is a medium-severity cross-site scripting vulnerability in harttle liquidjs, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. Versions 10.25.7 and below are vulnerable to XSS through a flaw in the strip_html filter logic. The strip_html filter is intended to remove HTML tags from a string before rendering, and is widely used as an XSS sanitizer. The implementation uses a regex whose catch-all branch (<.*?>) does not match line terminators, so any HTML tag containing a \n or \r character passes through unmodified. An attacker who can place a newline inside a tag (e.g. <img\nsrc=x\nonerror=alert(1)>) bypasses sanitization entirely, since browsers treat newlines as whitespace within a tag and execute the resulting onerror/onload/etc. handler. Exploitation is possible for applications that both render attacker-controlled strings via {{ x | strip_html }} to defend against HTML injection and do not separately HTML-escape that output (default behavior — outputEscape is unset by default). This issue has been fixed in version 10.26.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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

Upgrade liquidjs to 10.26.0 or later.

## Is CVE-2026-44644 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44644 is a medium-severity cross-site scripting vulnerability in harttle liquidjs, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44644 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-44644/ (Markdown: https://insights.sbomify.com/CVE-2026-44644/index.md)
```

## Sources

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

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