{"answers":{"affected":"2 open source packages ship an affected version, including liquidjs.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45617 exists.","fix":"Upgrade liquidjs to 10.26.0 or later.","what":"CVE-2026-45617 is a high-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45617 and fix it if it is affected.\n\nWhat it is: CVE-2026-45617 is a high-severity denial of service vulnerability in harttle liquidjs, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45617 exists.\n\nAffected packages and fixed versions:\n- liquidjs (npm): affected all versions; fixed in 10.26.0\n- liquidjs (npm): affected all versions; fixed in 10.26.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45617/ (Markdown: https://insights.sbomify.com/CVE-2026-45617/index.md)","id":"CVE-2026-45617","markdown":"https://insights.sbomify.com/CVE-2026-45617/index.md","name":"CVE-2026-45617","record":{"aliases":["ECHO-25d0-5f90-77b5","GHSA-r7g9-xpmj-5fcq","MINI-7ffw-67vx-4q5v","MINI-hf2w-6fq8-pw27","MINI-j548-8jwf-465h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript template engine","requires_auth":"none","summary":"An attacker can cause severe CPU exhaustion and event-loop blocking in Node.js applications using LiquidJS by sending crafted input to the strip_html filter.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"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 \u003cscript, \u003cstyle, or \u003c!-- opener tokens without matching closers, the V8 regex engine performs O(N²) backtracking, blocking the Node.js event loop. A single ~350 KB request ('\u003cscript'.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 — 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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"LiquidJS: ReDoS via Quadratic Backtracking in `strip_html` Filter Regex","id":"CVE-2026-45617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"LiquidJS is Vulnerable to Remote Code Execution","id":"CVE-2026-45618"},"packages":[{"ecosystem":"npm","fixed":["10.26.0"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":null,"source":"GHSA-r7g9-xpmj-5fcq"},{"ecosystem":"npm","fixed":["10.26.0"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":"pkg:npm/liquidjs","source":"GHSA-r7g9-xpmj-5fcq"}],"prev":{"headline":"Vvveb: Stored XSS in Posts allows privilege escalation via post editor","id":"CVE-2026-45616"},"products":["liquidjs"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-18","vendors":["harttle"]},"summary":"An attacker can cause severe CPU exhaustion and event-loop blocking in Node.js applications using LiquidJS by sending crafted input to the strip_html filter.","url":"https://insights.sbomify.com/CVE-2026-45617/"}