CVE-2026-45617: CWE-1333: Inefficient Regular Expression Complexity in harttle liquidjs
LiquidJS versions 10.25.7 and below contain a vulnerability in the strip_html filter where a flawed regular expression causes quadratic backtracking. This leads to a ReDoS (Regular Expression Denial of Service) attack that can block the Node.js event loop and cause high CPU usage. The issue is triggered by input containing many unclosed <script, <style, or <!-- tokens. The vulnerability allows unauthenticated attackers to cause severe event-loop blocking and CPU saturation. The issue is fixed in version 10.26.0.
AI Analysis
Technical Summary
LiquidJS, a JavaScript template engine, has a ReDoS vulnerability (CWE-1333) in versions 10.25.7 and earlier. The built-in strip_html filter uses a regex with four flawed lazy-quantified alternatives, causing quadratic backtracking in the V8 regex engine when processing inputs with many unclosed <script, <style, or <!-- tokens. This results in O(N²) complexity, blocking the Node.js event loop and causing CPU amplification. The default memoryLimit setting does not limit regex CPU usage, allowing an attacker to stall the process with crafted input. The vulnerability can be exploited by a single unauthenticated request. The issue is resolved in version 10.26.0.
Potential Impact
An unauthenticated attacker can send specially crafted input to trigger the inefficient regex in the strip_html filter, causing the Node.js event loop to block for several seconds and saturate CPU resources. This leads to denial of service by making the application unresponsive. Memory limits do not mitigate the CPU exhaustion caused by the regex backtracking. The impact is high availability disruption without direct confidentiality or integrity loss.
Mitigation Recommendations
Upgrade to LiquidJS version 10.26.0 or later where this vulnerability is fixed. Until then, avoid processing untrusted input with the strip_html filter or implement external request rate limiting to reduce exposure. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in version 10.26.0.
CVE-2026-45617: CWE-1333: Inefficient Regular Expression Complexity in harttle liquidjs
Description
LiquidJS versions 10.25.7 and below contain a vulnerability in the strip_html filter where a flawed regular expression causes quadratic backtracking. This leads to a ReDoS (Regular Expression Denial of Service) attack that can block the Node.js event loop and cause high CPU usage. The issue is triggered by input containing many unclosed <script, <style, or <!-- tokens. The vulnerability allows unauthenticated attackers to cause severe event-loop blocking and CPU saturation. The issue is fixed in version 10.26.0.
CVSS v3.1
Score 7.5high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
LiquidJS, a JavaScript template engine, has a ReDoS vulnerability (CWE-1333) in versions 10.25.7 and earlier. The built-in strip_html filter uses a regex with four flawed lazy-quantified alternatives, causing quadratic backtracking in the V8 regex engine when processing inputs with many unclosed <script, <style, or <!-- tokens. This results in O(N²) complexity, blocking the Node.js event loop and causing CPU amplification. The default memoryLimit setting does not limit regex CPU usage, allowing an attacker to stall the process with crafted input. The vulnerability can be exploited by a single unauthenticated request. The issue is resolved in version 10.26.0.
Potential Impact
An unauthenticated attacker can send specially crafted input to trigger the inefficient regex in the strip_html filter, causing the Node.js event loop to block for several seconds and saturate CPU resources. This leads to denial of service by making the application unresponsive. Memory limits do not mitigate the CPU exhaustion caused by the regex backtracking. The impact is high availability disruption without direct confidentiality or integrity loss.
Mitigation Recommendations
Upgrade to LiquidJS version 10.26.0 or later where this vulnerability is fixed. Until then, avoid processing untrusted input with the strip_html filter or implement external request rate limiting to reduce exposure. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in version 10.26.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-12T20:31:43.448Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a332119f198dc38c11faa5a
Added to database: 06/17/2026, 22:35:05 UTC
Last enriched: 07/10/2026, 09:51:27 UTC
Last updated: 07/18/2026, 20:59:43 UTC
Views: 76
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.
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.