LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.
Summary
LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the renderLimit option can be fully bypassed by a {% for %} (or {% tablerow %}) tag whose body is empty. The renderLimit option is documented in docs/source/tutorials/dos.md as the mechanism that "mitigates this by limiting the time consumed by each render() call." The per-iteration time check is reached only when the body contains at least one template node, so a template such as {%- for i in (1..N) -%}{%- endfor -%} iterates the full collection without ever consulting renderLimit. With a configured renderLimit of 50 ms, a single parseAndRenderSync call has been observed to consume 2.26 seconds (~45× over the limit) and scales linearly with N up to memoryLimit, allowing a low-privileged template author to wedge an event-loop thread for an attacker-chosen duration. Deployments that rely on a finite renderLimit for DoS protection (common in multi-tenant template-authoring environments) can still be forced by a single crafted template to monopolize a Node.js event-loop worker for attacker-controlled time, potentially stalling in-flight requests, with availability impact only. 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
- No
- 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-8xx9-69p8-7jp3 |
- 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-8xx9-69p8-7jp3
Remediation
- Fix · CNA liquidjs (harttle) Fixed in 10.26.0
- Fix · GHSA-8xx9-69p8-7jp3 liquidjs (npm) Fixed in 10.26.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-44645
- 2026-10-03 Alias added: GHSA-8xx9-69p8-7jp3
References
Other 5
- https://github.com/harttle/liquidjs/security/advisories/GHSA-8xx9-69p8-7jp3
- https://github.com/harttle/liquidjs/commit/5b9c3469085e01c79e2d0af28e2a13f730e1793d
- 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-44645 · CVE Program
- CVE-2026-44645 · NVD
- FIRST EPSS
- GHSA-8xx9-69p8-7jp3 · 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