{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-9f72-qcpw-2hxc in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.24 or later.","what":"GHSA-9f72-qcpw-2hxc is a path traversal vulnerability in openclaw, published on 3 Mar 2026."},"fix_prompt":"Check this codebase for GHSA-9f72-qcpw-2hxc and fix it if it is affected.\n\nWhat it is: GHSA-9f72-qcpw-2hxc is a path traversal vulnerability in openclaw, published on 3 Mar 2026. \nExploitation: There is no known exploitation of GHSA-9f72-qcpw-2hxc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.24\n- openclaw (npm): affected all versions; fixed in 2026.2.24\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/GHSA-9f72-qcpw-2hxc/ (Markdown: https://insights.sbomify.com/GHSA-9f72-qcpw-2hxc/index.md)","id":"GHSA-9f72-qcpw-2hxc","markdown":"https://insights.sbomify.com/GHSA-9f72-qcpw-2hxc/index.md","name":"GHSA-9f72-qcpw-2hxc","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"unknown","non_default_config":true,"product_category":"OpenClaw npm package","requires_auth":"none","summary":"Attackers can read files outside the workspace in sandboxed runs if workspaceOnly is enabled, bypassing path restrictions for image loading.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nIn sandboxed runs, native prompt image auto-load did not honor `tools.fs.workspaceOnly=true`.\n\nThis optional hardening setting is **not enabled by default**. When operators enabled it, prompt text could still reference mounted out-of-workspace image paths (for example `/agent/secret.png`) and load those image bytes for vision-capable model input.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Latest published npm version at triage time: `2026.2.23`\n- Vulnerable version range: `\u003c= 2026.2.23`\n- Patched version (planned next release): `2026.2.24`\n\n### Conditions Required\nThis issue required all of the following:\n- sandbox mode enabled,\n- `tools.fs.workspaceOnly=true` configured,\n- an out-of-workspace mount path reachable from the sandbox (for example `/agent`),\n- vision-capable model path active for native prompt image loading.\n\n### Technical Details\nNative prompt image ingestion (`detectAndLoadPromptImages` / `loadImageFromRef`) resolved and read sandbox paths but did not apply the same workspace-root assertion used by file tools when `tools.fs.workspaceOnly` was set.\n\n### Fix Commit(s)\n- `370d115549c0dadace0902775eea0d5094aedfdc`\n\n### Verification\n- `pnpm check`\n- `pnpm exec vitest run --config vitest.gateway.config.ts`\n- `pnpm test:fast`\n\n### Release Process Note\n`patched_versions` is pre-set to the planned next release (`2026.2.24`) so once npm release is available, this advisory only needs publish action.\n\nOpenClaw thanks @tdjackey for reporting.\n\n### Publication Update (2026-02-25)\n`openclaw@2026.2.24` is published on npm and contains the fix commit(s) listed above. This advisory now marks `\u003e= 2026.2.24` as patched.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"OpenClaw: Native prompt image auto-load did not honor tools.fs.workspaceOnly in sandboxed runs","id":"GHSA-9f72-qcpw-2hxc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["2026.2.24"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-9f72-qcpw-2hxc"},{"ecosystem":"npm","fixed":["2026.2.24"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-9f72-qcpw-2hxc"}],"products":null,"published":"2026-03-03","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can read files outside the workspace in sandboxed runs if workspaceOnly is enabled, bypassing path restrictions for image loading.","url":"https://insights.sbomify.com/GHSA-9f72-qcpw-2hxc/"}