High severity · published Apr 8, 2026
CVE-2026-39859
LiquidJS has a renderFile() / parseFile() bypass configured root and allow arbitrary file read
7.5
CVSS
0.4%
EPSS
No
On KEV
Description
LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.3, liquidjs 10.25.0 documents root as constraining filenames passed to renderFile() and parseFile(), but top-level file loads do not enforce that boundary. A Liquid instance configured with an empty temporary directory as root can return the contents of arbitrary files. This vulnerability is fixed in 10.25.3.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 39% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LI
liquidjs · harttle
< 10.25.3 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-39859
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-39859
Vendor Advisory
https://github.com/harttle/liquidjs/security/advisories/GHSA-v273-448j-v4qj
More from liquidjs
10.0
CVE-2026-45618
LiquidJS is Vulnerable to Remote Code Execution
8.7
CVE-2026-61556
LiquidJS: An infinite loop vulnerability in `strip_html` filter
8.2
CVE-2026-55575
LiquidJS: `pop` filter bypasses `memoryLimit` accounting that its array-filter siblings enforce
7.5
CVE-2026-69222
LiquidJS: Uncontrolled Resource Consumption in `join` filter allows template authors to bypass `memoryLimit` and crash the process
7.5
CVE-2026-45357
LiquidJS: Memory and render limit bypass via unbounded width padding in `date` filter (strftime)