CVE-2026-39859: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in harttle liquidjs
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.
AI Analysis
Technical Summary
LiquidJS, a JavaScript template engine compatible with Shopify and GitHub Pages, prior to version 10.25.3, improperly limits pathname access in its renderFile() and parseFile() functions. Although the root directory is documented as a constraint, top-level file loads bypass this restriction. Consequently, when a Liquid instance is configured with an empty temporary directory as root, it can return contents of arbitrary files outside the intended directory. This constitutes a CWE-22 path traversal vulnerability. The issue is resolved in LiquidJS version 10.25.3.
Potential Impact
An attacker can exploit this vulnerability to read arbitrary files on the system where LiquidJS is running, potentially exposing sensitive information. The vulnerability does not require privileges or user interaction and has a medium severity score of 6.3. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade LiquidJS to version 10.25.3 or later, where this path traversal vulnerability is fixed. Since no official patch links or vendor advisories are provided beyond the version fix, users should verify their LiquidJS version and update accordingly. No additional mitigations are indicated.
CVE-2026-39859: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in harttle liquidjs
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
LiquidJS, a JavaScript template engine compatible with Shopify and GitHub Pages, prior to version 10.25.3, improperly limits pathname access in its renderFile() and parseFile() functions. Although the root directory is documented as a constraint, top-level file loads bypass this restriction. Consequently, when a Liquid instance is configured with an empty temporary directory as root, it can return contents of arbitrary files outside the intended directory. This constitutes a CWE-22 path traversal vulnerability. The issue is resolved in LiquidJS version 10.25.3.
Potential Impact
An attacker can exploit this vulnerability to read arbitrary files on the system where LiquidJS is running, potentially exposing sensitive information. The vulnerability does not require privileges or user interaction and has a medium severity score of 6.3. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade LiquidJS to version 10.25.3 or later, where this path traversal vulnerability is fixed. Since no official patch links or vendor advisories are provided beyond the version fix, users should verify their LiquidJS version and update accordingly. No additional mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-07T19:13:20.379Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d6b51c1cc7ad14daaa5ce9
Added to database: 4/8/2026, 8:05:48 PM
Last enriched: 4/16/2026, 11:59:09 AM
Last updated: 5/24/2026, 10:53:20 AM
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.