{"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-44646 exists.","fix":"Upgrade liquidjs to 10.26.0 or later.","what":"CVE-2026-44646 is a medium-severity 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-44646 and fix it if it is affected.\n\nWhat it is: CVE-2026-44646 is a medium-severity 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-44646 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-44646/ (Markdown: https://insights.sbomify.com/CVE-2026-44646/index.md)","id":"CVE-2026-44646","markdown":"https://insights.sbomify.com/CVE-2026-44646/index.md","name":"CVE-2026-44646","record":{"aliases":["ECHO-3d18-f7d2-d0b9","GHSA-9x9p-qf8f-mvjg","MINI-567w-g773-m59g","MINI-fqv3-m39p-pfc7","MINI-rrq9-fg4c-66w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript template engine","requires_auth":"none","summary":"LiquidJS allows prototype chain property leakage in render partials when per-render security options are ignored, bypassing intended access controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, Context.spawn() creates a child Context for the {% render %} tag but does not propagate the parent context's resolved ownPropertyOnly value, resulting in a silent bypass. The new context re-derives ownPropertyOnly from opts.ownPropertyOnly (the instance-level option), silently discarding any RenderOptions.ownPropertyOnly override that was supplied to parseAndRender(). As a result, a developer who runs a Liquid instance with the backwards-compatible ownPropertyOnly:false and then locks down an untrusted render with parseAndRender(..., { ownPropertyOnly: true }) still leaks prototype-chain properties from inside any {% render %} partial. This is a distinct exploit surface from the previously identified array-filter variants (where, reject, group_by, find, find_index, has) — the underlying root cause in Context.spawn() is shared, but {% render %} is a separately reachable sink that needs no filter usage. 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: `{% render %}` tag silently bypasses per-render `ownPropertyOnly:true` via `Context.spawn()`","id":"CVE-2026-44646","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OneDev: Path Traversal (read capability via Git LFS pointer resolution)","id":"CVE-2026-44647"},"packages":[{"ecosystem":"npm","fixed":["10.26.0"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":null,"source":"GHSA-9x9p-qf8f-mvjg"},{"ecosystem":"npm","fixed":["10.26.0"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":"pkg:npm/liquidjs","source":"GHSA-9x9p-qf8f-mvjg"}],"prev":{"headline":"LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body","id":"CVE-2026-44645"},"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":"LiquidJS allows prototype chain property leakage in render partials when per-render security options are ignored, bypassing intended access controls.","url":"https://insights.sbomify.com/CVE-2026-44646/"}