{"answers":{"affected":"2 open source packages ship an affected version, including liquidjs. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33285 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33285 is a high-severity denial of service vulnerability in harttle liquidjs, published on 26 Mar 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-33285 and fix it if it is affected.\n\nWhat it is: CVE-2026-33285 is a high-severity denial of service vulnerability in harttle liquidjs, published on 26 Mar 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-33285 exists.\n\nAffected packages and fixed versions:\n- liquidjs (npm): affected all versions up to 10.24.0; no fix listed\n- liquidjs (npm): affected all versions up to 10.24.0; no fix listed\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-33285/ (Markdown: https://insights.sbomify.com/CVE-2026-33285/index.md)","id":"CVE-2026-33285","markdown":"https://insights.sbomify.com/CVE-2026-33285/index.md","name":"CVE-2026-33285","record":{"aliases":["GHSA-9r5m-9576-7f6x","MINI-25wf-pp5r-m3j2","MINI-3w8r-ghx2-wpgh"],"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 crash the Node.js process by bypassing memory limits with reverse range expressions in LiquidJS templates.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"liquidjs","vendor":"liquidjs"}],"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-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to version 10.25.1, LiquidJS's `memoryLimit` security mechanism can be completely bypassed by using reverse range expressions (e.g., `(100000000..1)`), allowing an attacker to allocate unlimited memory. Combined with a string flattening operation (e.g., `replace` filter), this causes a V8 Fatal error that crashes the Node.js process, resulting in complete denial of service from a single HTTP request. Version 10.25.1 patches the issue.","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: memoryLimit Bypass through Negative Range Values Leads to Process Crash","id":"CVE-2026-33285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Graphiti Affected by Arbitrary Method Execution via Unvalidated Relationship Names","id":"CVE-2026-33286"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["10.24.0"],"package":"liquidjs","purl":null,"source":"GHSA-9r5m-9576-7f6x"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["10.24.0"],"package":"liquidjs","purl":"pkg:npm/liquidjs","source":"GHSA-9r5m-9576-7f6x"}],"prev":{"headline":"GlobalLeaks has insufficient URL validation in user support API","id":"CVE-2026-33284"},"products":["liquidjs"],"published":"2026-03-26","related":[{"cvss_score":8.7,"headline":"liquidjs has a path traversal fallback vulnerability","id":"CVE-2026-30952","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":8.2,"headline":"LiquidJS has a root restriction bypass for partial and layout loading through symlinked templates","id":"CVE-2026-35525","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"LiquidJS is vulnerable to Denial of Service via circular block reference in layout","id":"CVE-2026-41311","kev_date_added":null,"published":"2026-05-09"},{"cvss_score":7.5,"headline":"LiquidJS has Exponential Memory Amplification through its replace_first Filter $\u0026 Pattern","id":"CVE-2026-33287","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":6.3,"headline":"LiquidJS has a renderFile() / parseFile() bypass configured root and allow arbitrary file read","id":"CVE-2026-39859","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":5.3,"headline":"LiquidJS: ownPropertyOnly bypass via sort_natural filter — prototype property information disclosure through sorting side-channel","id":"CVE-2026-39412","kev_date_added":null,"published":"2026-04-08"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-03-28","vendors":["harttle"]},"summary":"Attackers can crash the Node.js process by bypassing memory limits with reverse range expressions in LiquidJS templates.","url":"https://insights.sbomify.com/CVE-2026-33285/"}