Quick answers
- Is CVE-2026-39412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39412 being exploited in the wild.
- How severe is CVE-2026-39412?
- Medium severity, with a CVSS score of 5.3, published 8 April 2026.
- Which products and versions are affected?
- liquidjs (npm) SEMVER:introduced=0,fixed=10.25.4.
- Is there a fix for CVE-2026-39412?
- Yes. liquidjs (npm): upgrade to 10.25.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39412 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-39412?
- 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.25.4 or later
npm install liquidjs@10.25.4
Technical details
A vulnerability exists in LiquidJS where the 'sort' and 'sort_natural' filters bypass the 'ownPropertyOnly' security configuration. The root cause is the use of direct bracket notation (lhs[propertyString]) in the array filter implementation, which traverses the JavaScript prototype chain instead of using the library's internal scope-safe property accessors. An attacker with the ability to author templates can exploit this via a sorting side-channel attack to infer the values of inherited prototype properties. This can lead to the disclosure of sensitive information like API keys or internal tokens in multi-tenant environments. The issue is fixed in version 10.25.4 by utilizing the '_getFromScope' helper to enforce property boundaries.
Affected products
- harttle liquidjs < 10.25.4
Identifiers
- CVE-2026-39412
- GHSA-rv5g-f82m-qrvv
Timeline
- 2026-04-07: patched: Fix committed and version 10.25.4 released.
- 2026-04-08: disclosed: Security advisory published.