{"answers":{"affected":"2 open source packages ship an affected version, including openclaw. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41364 in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.3.31 or later.","what":"CVE-2026-41364 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41364 and fix it if it is affected.\n\nWhat it is: CVE-2026-41364 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41364 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.3.31\n- openclaw (npm): affected all versions; fixed in 2026.3.31\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-41364/ (Markdown: https://insights.sbomify.com/CVE-2026-41364/index.md)","id":"CVE-2026-41364","markdown":"https://insights.sbomify.com/CVE-2026-41364/index.md","name":"CVE-2026-41364","record":{"aliases":["GHSA-fv94-qvg8-xqpw","MINI-f8jm-7fjj-43vw","MINI-mx74-9c65-f4qg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenClaw SSH sandbox","requires_auth":"low_privilege","summary":"Remote attackers can write arbitrary files and escape the sandbox by uploading tar archives with symlinks, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"openclaw","vendor":"openclaw"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"OpenClaw before 2026.3.31 contains a symlink following vulnerability in SSH sandbox tar upload that allows remote attackers to write arbitrary files. Attackers can exploit this by uploading tar archives containing symlinks to escape the sandbox and overwrite files on the remote host.","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":"OpenClaw \u003c 2026.3.31 - Arbitrary File Write via Symlink Following in SSH Sandbox Tar Upload","id":"CVE-2026-41364","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"openclaw:openclaw","products":["openclaw:openclaw"],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OpenClaw \u003c 2026.3.31 - Sender Allowlist Bypass via Graph API Thread History","id":"CVE-2026-41365"},"packages":[{"ecosystem":"npm","fixed":["2026.3.31"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-fv94-qvg8-xqpw"},{"ecosystem":"npm","fixed":["2026.3.31"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-fv94-qvg8-xqpw"}],"prev":{"headline":"OpenClaw 2026.2.6 \u003c 2026.3.28 - Arbitrary File Read via Feishu upload_image Parameter","id":"CVE-2026-41363"},"products":["OpenClaw"],"published":"2026-04-27","related":[{"cvss_score":9.9,"headline":"Security feature bypass in OpenClaw","id":"CVE-2026-28363","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2026-30741","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval","id":"CVE-2026-33579","kev_date_added":null,"published":"2026-03-31"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate","id":"CVE-2026-32922","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.11 - Approval Bypass via Unrecognized Script Runners","id":"CVE-2026-32978","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.12 - Scope Elevation in WebSocket Shared-Auth Connections","id":"CVE-2026-22172","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.2.14 - Remote Code Execution via Node Invoke Approval Bypass","id":"CVE-2026-28466","kev_date_added":null,"published":"2026-03-05"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["OpenClaw"]},"summary":"Remote attackers can write arbitrary files and escape the sandbox by uploading tar archives with symlinks, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-41364/"}