Quick answers
- Is CVE-2026-45618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45618 being exploited in the wild.
- How severe is CVE-2026-45618?
- Critical severity, with a CVSS score of 10, published 11 August 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-45618?
- 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-45618 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45618?
- 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
LiquidJS is vulnerable to Remote Code Execution (RCE) due to improper isolation during template evaluation. An attacker can use the `valueOf` filter to obtain a reference to the internal `this` context (the scope). By leveraging 'comparable' gadgets and prototype pollution techniques within the template, an attacker can overwrite internal properties such as `this.loader.lookup` and `this.readFile`. This allows the attacker to manipulate the `_parseFile` generator to obtain a reference to the `Function` constructor, enabling the execution of arbitrary JavaScript code. The vulnerability is patched in version 10.26.0.
Affected products
- harttle liquidjs < 10.26.0
Identifiers
- CVE-2026-45618
- GHSA-gf2q-c269-pqgc
Timeline
- 2026-05-24: disclosed
- 2026-05-27: advisory