CVE-2026-35525
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk32th percentile - higher than 32% of all known CVEs
Summary
LiquidJS before version 10.25.3 has a path restriction bypass vulnerability in {% include %}, {% render %}, and {% layout %} directives. The containment check is path-based, not realpath-based, so a symlink inside the allowed root pointing outside bypasses the restriction.
Risk Assessment
An attacker who can place template files in a trusted directory (e.g., via uploaded themes, extracted archives, or repository content) can use symlinks to read and render files outside the allowed root, leading to sensitive data exposure.
Recommendation
Upgrade LiquidJS to version 10.25.3 or later immediately, which fixes this vulnerability.
Other vulnerabilities in LiquidJS
See all- CVE-2026-45618Critical
LiquidJS is a Shopify/GitHub Pages compatible template engine. Prior to version 10.26.0, it is possible to execute arbitrary code with crafted templates. Version 10.26.0 patches the issue.
- CVE-2026-69222High
In LiquidJS before 10.27.2, the join filter in src/filters/array.ts computes complexity from array length and separator length instead of the total string length. The concat filter can cheaply double arrays, and join then materializes content while charging only for element count, allowing a template to exceed memoryLimit. The array_to_sentence_string filter has a similar defect, potentially crashing the process.
- CVE-2026-61556High
In LiquidJS from 10.26.0 to 10.27.1, the strip_html filter can enter an infinite loop when the input contains '<', has at least one preceding character, and no later '>'. This blocks template rendering and can cause denial of service with input as short as 'a<'.
- CVE-2026-55575High
In LiquidJS prior to version 10.27.1, the 'pop' array filter allocates a full clone of the input array without respecting the memoryLimit budget. This allows a template render like {{ huge_array | pop }} to allocate memory outside the configured limit.
- CVE-2026-45617High
LiquidJS is a Shopify/GitHub Pages compatible template engine that in versions 10.25.7 and below contains a flawed regex in the strip_html filter. This leads to ReDoS attacks via quadratic backtracking, blocking the Node.js event loop.
- CVE-2026-45357High
In versions 10.25.7 and below of the LiquidJS template engine, a vulnerability exists related to the date filter that improperly processes width specifiers, leading to unbounded string concatenation and bypassing memory and render limits.
- CVE-2026-44646Medium
In versions 10.25.7 and below, the LiquidJS template engine incorrectly propagates the ownPropertyOnly value from the parent context, leading to a silent bypass. As a result, developers may inadvertently expose prototype-chain properties in unsafe renders.
- CVE-2026-44645Medium
In versions 10.25.7 and below of the LiquidJS template engine, the renderLimit option can be fully bypassed by using an empty {% for %} or {% tablerow %} tag. This allows for unlimited rendering time consumption, potentially leading to DoS attacks.
- CVE-2026-44644Medium
LiquidJS, a template engine compatible with Shopify/GitHub Pages, has a vulnerability to XSS in versions 10.25.7 and below due to a flaw in the strip_html filter logic. This flaw allows bypassing HTML sanitization, enabling attackers to inject malicious code.
- CVE-2026-41311High
LiquidJS before version 10.25.7 is vulnerable to a DoS attack via circular block references in {% layout %} / {% block %}, causing memory exhaustion and Node.js process crash.
Original NVD description (English source)
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.