CVE-2026-45617

{"id": "CVE-2026-45617", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-45617", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-18T15:46:01.767622Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "harttle", "product": "liquidjs", "versions": [{"status": "affected", "version": "< 10.26.0"}]}]}], "published": "2026-06-17T23:17:04.033", "references": [{"url": "https://github.com/harttle/liquidjs/commit/3616a744b9abeb425c217b340a2397d46176afb8", "source": "security-advisories@github.com"}, {"url": "https://github.com/harttle/liquidjs/releases/tag/v10.26.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/harttle/liquidjs/security/advisories/GHSA-r7g9-xpmj-5fcq", "source": "security-advisories@github.com"}, {"url": "https://github.com/harttle/liquidjs/security/advisories/GHSA-r7g9-xpmj-5fcq", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-1333"}]}], "descriptions": [{"lang": "en", "value": "LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the built-in strip_html filter uses a regex containing four flawed lazy-quantified alternatives, leading to ReDoS via quadratic backtracking. When the input contains many <script, <style, or <!-- opener tokens without matching closers, the V8 regex engine performs O(N\u00b2) backtracking, blocking the Node.js event loop. A single ~350 KB request ('<script'.repeat(50000)) stalls the process for ~10 seconds; cost grows quadratically with input size. The default memoryLimit: Infinity does not bound regex CPU, and even when configured strip_html only charges str.length to the limit \u2014 the regex itself runs unbounded. A single unauthenticated request containing crafted untrusted input can cause severe event-loop blocking and CPU amplification that saturates Node.js workers while bypassing memoryLimit protections. This issue has been fixed in version 10.26.0."}, {"lang": "es", "value": "LiquidJS es un motor de plantillas compatible con Shopify/GitHub Pages escrito en JavaScript puro. En las versiones 10.25.7 e inferiores, el filtro incorporado strip_html utiliza una expresi\u00f3n regular (regex) que contiene cuatro alternativas cuantificadas perezosamente defectuosas, lo que lleva a ReDoS a trav\u00e9s de retroceso cuadr\u00e1tico. Cuando la entrada contiene muchos tokens de apertura <script, <style o [comment] sin sus cierres correspondientes, el motor de expresiones regulares V8 realiza un retroceso O(N\u00b2), bloqueando el bucle de eventos de Node.js. Una \u00fanica solicitud de ~350 KB (\u2019<script\u2019.repeat(50000)) detiene el proceso durante ~10 segundos; el costo crece cuadr\u00e1ticamente con el tama\u00f1o de la entrada. El memoryLimit: Infinity predeterminado no limita la CPU de la expresi\u00f3n regular, e incluso cuando est\u00e1 configurado, strip_html solo carga str.length al l\u00edmite - la expresi\u00f3n regular en s\u00ed se ejecuta sin l\u00edmites. Una \u00fanica solicitud no autenticada que contenga una entrada no confiable manipulada puede causar un bloqueo severo del bucle de eventos y una amplificaci\u00f3n de la CPU que satura los trabajadores de Node.js mientras elude las protecciones de memoryLimit. Este problema ha sido solucionado en la versi\u00f3n 10.26.0."}], "lastModified": "2026-10-25T23:10:00.167", "sourceIdentifier": "security-advisories@github.com"}