CVE-2026-39859 LiquidJS has a renderFile() / parseFile() bypass configured root and allow arbitrary file read

Medium 6.3 Published Updated

LiquidJS allows arbitrary file read via renderFile/parseFile when root is configured, enabling attackers to access sensitive files.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-39859?

CVE-2026-39859 is a medium-severity path traversal vulnerability in harttle liquidjs, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-22

Which versions are affected by CVE-2026-39859?

2 open source packages ship an affected version, including liquidjs. It affects 1 product.

PackageAffectedFixed in
liquidjs npmAll versions10.25.5
liquidjs npmAll versions10.25.5

Products include Liquidjs Liquidjs.

How do I fix CVE-2026-39859?

Upgrade liquidjs to 10.25.5 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-39859 being exploited?

There is no known exploitation of CVE-2026-39859 in the wild and no public exploit code.

Sources

Also known as GHSA-v273-448j-v4qj, MINI-4vcm-x9m2-6rqm, MINI-pp56-3r3r-6652.

Is CVE-2026-39859 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free