Quick answers
- Is CVE-2026-44645 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44645 being exploited in the wild.
- How severe is CVE-2026-44645?
- Medium severity, with a CVSS score of 6.5, published 17 June 2026.
- Which products and versions are affected?
- liquidjs (npm) <= 10.25.7, SEMVER:introduced=0,last_affected=10.25.7.
- Is there a fix for CVE-2026-44645?
- A patch was published on 2026-05-14: Version 10.26.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44645 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44645?
- 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.
Technical details
A vulnerability in LiquidJS versions 10.25.7 and below allows for uncontrolled resource consumption (CWE-400). The 'renderLimit' option, intended to bound the execution time of template rendering, is only checked within the loop that processes template nodes. By providing a '{% for %}' or '{% tablerow %}' tag with an empty body, an attacker can force the engine to iterate through a large collection without ever triggering the time-limit check. This bypasses the wall-clock budget and allows a single render call to monopolize the Node.js event loop for an attacker-controlled duration, scaling linearly with the size of the collection. The issue is fixed in version 10.26.0 by moving the limit check to the entry point of the rendering function.
Affected products
- harttle liquidjs <= 10.25.7
Identifiers
- CVE-2026-44645
- GHSA-8xx9-69p8-7jp3
Timeline
- 2026-05-14: patched: Version 10.26.0 released
- 2026-05-24: advisory: GitHub Security Advisory published
- 2026-06-17: disclosed: CVE-2026-44645 published