Event-loop stall via unchecked empty loop bodies
Published Jun 17, 2026 · Updated Jun 17, 2026
Resource exhaustion in LiquidJS 10.25.7 and earlier allows remote authenticated users to stall a Node.js worker via crafted templates. Render.renderTemplates checks renderLimit only inside its template-node loop, so empty for or tablerow bodies run every range iteration without a time check. Exposure requires a finite renderLimit and attacker-controlled template input; a large range monopolizes one event-loop thread and stalls in-flight requests without reading or changing data.
Summary
What happened
Resource exhaustion in LiquidJS 10.25.7 and earlier allows remote authenticated users to stall a Node.js worker via crafted templates. Render.renderTemplates checks renderLimit only inside its template-node loop, so empty for or tablerow bodies run every range iteration without a time check. Exposure requires a finite renderLimit and attacker-controlled template input; a large range monopolizes one event-loop thread and stalls in-flight requests without reading or changing data.
The record
- CVE
- CVE-2026-44645
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- LiquidJS
- Product
- LiquidJS
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 10.26.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-8xx9-69p8-7jp3 empty-loop proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo