{"answers":{"affected":"2 open source packages ship an affected version, including @gitlawb/openclaude. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35570 exists.","fix":"Upgrade @gitlawb/openclaude to 0.5.1 or later.","what":"CVE-2026-35570 is a high-severity path traversal vulnerability in Gitlawb openclaude, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35570 and fix it if it is affected.\n\nWhat it is: CVE-2026-35570 is a high-severity path traversal vulnerability in Gitlawb openclaude, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35570 exists.\n\nAffected packages and fixed versions:\n- @gitlawb/openclaude (npm): affected all versions; fixed in 0.5.1\n- @gitlawb/openclaude (npm): affected all versions; fixed in 0.5.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-35570/ (Markdown: https://insights.sbomify.com/CVE-2026-35570/index.md)","id":"CVE-2026-35570","markdown":"https://insights.sbomify.com/CVE-2026-35570/index.md","name":"CVE-2026-35570","record":{"aliases":["GHSA-m6rx-7pvw-2f73"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OpenClaude CLI","requires_auth":"low_privilege","summary":"Attackers can bypass sandbox restrictions to read arbitrary files via path traversal when auto-allow is enabled without deny rules.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openclaude","vendor":"gitlawb"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"OpenClaude is an open-source coding-agent command line interface for cloud and local model providers. Versions prior to 0.5.1 have a logic flaw in `bashToolHasPermission()` inside `src/tools/BashTool/bashPermissions.ts`. When the sandbox auto-allow feature is active and no explicit deny rule is configured, the function returns an `allow` result immediately — before the path constraint filter (`checkPathConstraints`) is ever evaluated. This allows commands containing path traversal sequences (e.g., `../../../../../etc/passwd`) to bypass directory restrictions entirely. Version 0.5.1 contains a patch for the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-04-04","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-04T11:15:05Z","kind":"github_poc","ref":"https://github.com/Rickidevs/CVE-2026-35570","stars":1,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"OpenClaude has Sandbox Bypass via Early-Exit Logic Flaw that Allows Path Traversal","id":"CVE-2026-35570","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Emissary has Stored XSS via Navigation Template Link Injection","id":"CVE-2026-35571"},"packages":[{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"@gitlawb/openclaude","purl":null,"source":"GHSA-m6rx-7pvw-2f73"},{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"@gitlawb/openclaude","purl":"pkg:npm/%40gitlawb/openclaude","source":"GHSA-m6rx-7pvw-2f73"}],"prev":{"headline":"ApostropheCMS: Stored XSS in SEO Fields Leads to Authenticated API Data Exposure in ApostropheCMS","id":"CVE-2026-35569"},"products":["openclaude"],"published":"2026-04-20","related":[{"cvss_score":9.3,"headline":"OpenClaude: Sandbox Bypass via Model-Controlled `dangerouslyDisableSandbox` Input","id":"CVE-2026-42074","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":6.5,"headline":"OpenClaude's MCP OAuth Callback: State Check Bypass via error Param Leads to DoS","id":"CVE-2026-42073","kev_date_added":null,"published":"2026-06-02"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["Gitlawb"]},"summary":"Attackers can bypass sandbox restrictions to read arbitrary files via path traversal when auto-allow is enabled without deny rules.","url":"https://insights.sbomify.com/CVE-2026-35570/"}