LiquidJS: `{% render %}` tag silently bypasses per-render `ownPropertyOnly:true` via `Context.spawn()`
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-693.
Summary
LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, Context.spawn() creates a child Context for the {% render %} tag but does not propagate the parent context's resolved ownPropertyOnly value, resulting in a silent bypass. The new context re-derives ownPropertyOnly from opts.ownPropertyOnly (the instance-level option), silently discarding any RenderOptions.ownPropertyOnly override that was supplied to parseAndRender(). As a result, a developer who runs a Liquid instance with the backwards-compatible ownPropertyOnly:false and then locks down an untrusted render with parseAndRender(..., { ownPropertyOnly: true }) still leaks prototype-chain properties from inside any {% render %} partial. This is a distinct exploit surface from the previously identified array-filter variants (where, reject, group_by, find, find_index, has) — the underlying root cause in Context.spawn() is shared, but {% render %} is a separately reachable sink that needs no filter usage. This issue has been fixed in version 10.26.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| harttle | liquidjs | before 10.26.0 | 10.26.0 | Patch available | CNA |
| — | liquidjs (npm) | before 10.26.0 | 10.26.0 | Patch available | GHSA-9x9p-qf8f-mvjg |
- liquidjs Vendorharttle Affected before 10.26.0 Fixed in 10.26.0 Patch available CNA
- liquidjs (npm) Vendor— Affected before 10.26.0 Fixed in 10.26.0 Patch available GHSA-9x9p-qf8f-mvjg
Remediation
- Fix · CNA liquidjs (harttle) Fixed in 10.26.0
- Fix · GHSA-9x9p-qf8f-mvjg liquidjs (npm) Fixed in 10.26.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-44646
- 2026-10-03 Alias added: GHSA-9x9p-qf8f-mvjg
References
Other 5
- https://github.com/harttle/liquidjs/security/advisories/GHSA-9x9p-qf8f-mvjg
- https://github.com/harttle/liquidjs/commit/dbbf6288030591bf6da28d8c1cce5a17bca97bb6
- https://github.com/harttle/liquidjs/releases/tag/v10.26.0
- https://github.com/harttle/liquidjs
- https://github.com/harttle/liquidjs/blob/v10.26.0/CHANGELOG.md
More harttle vulnerabilities
- TI-2026-33363 LiquidJS is Vulnerable to Remote Code Execution CVSS 3.1CRITICAL 10.0
- TI-2026-44110 LiquidJS: An infinite loop vulnerability in `strip_html` filter CVSS 4.0HIGH 8.7
- TI-2026-40114 LiquidJS: `pop` filter bypasses `memoryLimit` accounting that its array-filter siblings enforce CVSS 4.0HIGH 8.2
- TI-2026-33362 LiquidJS: ReDoS via Quadratic Backtracking in `strip_html` Filter Regex CVSS 3.1HIGH 7.5
- TI-2026-29912 LiquidJS is vulnerable to Denial of Service via circular block reference in layout CVSS 3.1HIGH 7.5
- TI-2026-28394 Information disclosure in harttle liquidjs CVSS 3.1HIGH 7.5
Sources
- CVE-2026-44646 · CVE Program
- CVE-2026-44646 · NVD
- FIRST EPSS
- GHSA-9x9p-qf8f-mvjg · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences