Quick answers
- Is CVE-2026-45617 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45617 being exploited in the wild.
- How severe is CVE-2026-45617?
- High severity, with a CVSS score of 7.5, published 17 June 2026.
- Which products and versions are affected?
- liquidjs (npm) < 10.26.0, SEMVER:introduced=0,fixed=10.26.0.
- Is there a fix for CVE-2026-45617?
- Yes. liquidjs (npm): upgrade to 10.26.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45617 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45617?
- Check whether you run liquidjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- liquidjs (npm): upgrade to 10.26.0 or later
npm install liquidjs@10.26.0
Technical details
The built-in `strip_html` filter in LiquidJS uses a regular expression with four lazy-quantified alternatives that exhibit quadratic backtracking (O(N²)) when processing inputs with many unclosed opener tokens (e.g., `<script`, `<style`, or `<!--`). Because the V8 regex engine performs exhaustive backtracking to find a matching closer that does not exist, the Node.js event loop becomes blocked, saturating CPU workers. A single unauthenticated request of approximately 350 KB can stall a process for 10 seconds, with the cost growing quadratically relative to input size. The vulnerability bypasses `memoryLimit` protections because the regex execution itself is unbounded. The issue was resolved in version 10.26.0 by replacing the regex with a linear single-pass scan.
Affected products
- harttle liquidjs <= 10.25.7
Identifiers
- CVE-2026-45617
- GHSA-r7g9-xpmj-5fcq
Timeline
- 2026-05-14: patched: Version 10.26.0 released with fix
- 2026-05-24: advisory: GitHub Security Advisory published
- 2026-06-17: disclosed: CVE-2026-45617 published to NVD