{"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-55575 exists.","fix":"Upgrade liquidjs to 10.27.1 or later.","what":"CVE-2026-55575 is a high-severity denial of service vulnerability in harttle liquidjs, published on 8 Jul 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-55575 and fix it if it is affected.\n\nWhat it is: CVE-2026-55575 is a high-severity denial of service vulnerability in harttle liquidjs, published on 8 Jul 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-55575 exists.\n\nAffected packages and fixed versions:\n- liquidjs (npm): affected all versions; fixed in 10.27.1\n- liquidjs (npm): affected all versions; fixed in 10.27.1\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-55575/ (Markdown: https://insights.sbomify.com/CVE-2026-55575/index.md)","id":"CVE-2026-55575","markdown":"https://insights.sbomify.com/CVE-2026-55575/index.md","name":"CVE-2026-55575","record":{"aliases":["GHSA-g357-x5c3-c72p","MINI-5pp5-2rr8-ghvq","MINI-7gfh-9r6g-92r4","MINI-j8w3-g69w-4whc"],"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":"Attackers can cause denial of service in LiquidJS by using the pop filter to bypass memory limits, leading to excessive resource consumption.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.1, the pop array filter at src/filters/array.ts allocated a full clone of its input array via [...toArray(v)] without calling this.context.memoryLimit.use(...), allowing a template render such as {{ huge_array | pop }} to allocate an O(N) clone of an attacker-influenced array outside the configured memoryLimit budget. This issue is fixed in version 10.27.1.","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: `pop` filter bypasses `memoryLimit` accounting that its array-filter siblings enforce","id":"CVE-2026-55575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"MaaAssistantArknights: PR-title expression injection in release-preparation.yml","id":"CVE-2026-55576"},"packages":[{"ecosystem":"npm","fixed":["10.27.1"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":null,"source":"GHSA-g357-x5c3-c72p"},{"ecosystem":"npm","fixed":["10.27.1"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":"pkg:npm/liquidjs","source":"GHSA-g357-x5c3-c72p"}],"prev":{"headline":"vLLM: ReDoS via structured_outputs.regex compiled without timeout in xgrammar and outlines backends","id":"CVE-2026-55574"},"products":["liquidjs"],"published":"2026-07-08","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":"total"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["harttle"]},"summary":"Attackers can cause denial of service in LiquidJS by using the pop filter to bypass memory limits, leading to excessive resource consumption.","url":"https://insights.sbomify.com/CVE-2026-55575/"}