CVE-2026-35525
LiquidJS is a Shopify / GitHub Pages compatible template engine in …
LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.3, for {% include %}, {% render %}, and {% layout %}, LiquidJS checks whether the candidate path is inside the configured partials or layouts roots before reading it. That check is path-based, not realpath-based. Because of that, a file like partials/link.liquid passes the directory containment check as long as its pathname is under the allowed root. If link.liquid is actually a symlink to a file outside the allowed root, the filesystem follows the symlink when the file is opened and LiquidJS renders the external target. So the restriction is applied to the path string that was requested, not to the file that is actually read. This matters in environments where an attacker can place templates or otherwise influence files under a trusted template root, including uploaded themes, extracted archives, mounted content, or repository-controlled template trees. This vulnerability is fixed in 10.25.3.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/harttle/liquidjs/security/advisories/GHSA-56p5-8mhr-2fph
- github.com/harttle/liquidjs/pull/867
- github.com/harttle/liquidjs/releases/tag/v10.25.3
- github.com/advisories/GHSA-56p5-8mhr-2fph
- nvd.nist.gov/vuln/detail/CVE-2026-35525
- nvd.nist.gov/vuln/detail/CVE-2026-35525
- cve.org/CVERecord?id=CVE-2026-35525
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.