{"answers":{"affected":"2 open source packages ship an affected version, including liquidjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-39859 in the wild and no public exploit code.","fix":"Upgrade liquidjs to 10.25.5 or later.","what":"CVE-2026-39859 is a medium-severity path traversal vulnerability in harttle liquidjs, published on 8 Apr 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-39859 and fix it if it is affected.\n\nWhat it is: CVE-2026-39859 is a medium-severity path traversal vulnerability in harttle liquidjs, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-39859 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- liquidjs (npm): affected all versions; fixed in 10.25.5\n- liquidjs (npm): affected all versions; fixed in 10.25.5\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-39859/ (Markdown: https://insights.sbomify.com/CVE-2026-39859/index.md)","id":"CVE-2026-39859","markdown":"https://insights.sbomify.com/CVE-2026-39859/index.md","name":"CVE-2026-39859","record":{"aliases":["GHSA-v273-448j-v4qj","MINI-4vcm-x9m2-6rqm","MINI-pp56-3r3r-6652"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript template engine","requires_auth":"none","summary":"LiquidJS allows arbitrary file read via renderFile/parseFile when root is configured, enabling attackers to access sensitive files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"liquidjs","vendor":"liquidjs"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.3, liquidjs 10.25.0 documents root as constraining filenames passed to renderFile() and parseFile(), but top-level file loads do not enforce that boundary. A Liquid instance configured with an empty temporary directory as root can return the contents of arbitrary files. This vulnerability is fixed in 10.25.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"LiquidJS has a renderFile() / parseFile() bypass configured root and allow arbitrary file read","id":"CVE-2026-39859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Nix sandbox escape: file write via symlink at FOD `.tmp` copy destination","id":"CVE-2026-39860"},"packages":[{"ecosystem":"npm","fixed":["10.25.5"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":null,"source":"GHSA-v273-448j-v4qj"},{"ecosystem":"npm","fixed":["10.25.5"],"introduced":["0"],"last_affected":[],"package":"liquidjs","purl":"pkg:npm/liquidjs","source":"GHSA-v273-448j-v4qj"}],"prev":{"headline":"Traefik: Forwarded alias spoofing top pre-auth decision bypass","id":"CVE-2026-39858"},"products":["liquidjs"],"published":"2026-04-08","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: memoryLimit Bypass through Negative Range Values Leads to Process Crash","id":"CVE-2026-33285","kev_date_added":null,"published":"2026-03-26"},{"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":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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-10","vendors":["harttle"]},"summary":"LiquidJS allows arbitrary file read via renderFile/parseFile when root is configured, enabling attackers to access sensitive files.","url":"https://insights.sbomify.com/CVE-2026-39859/"}