{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-8mf7-vv8w-hjr2 in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.22 or later.","what":"GHSA-8mf7-vv8w-hjr2 is a command injection vulnerability in openclaw, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-8mf7-vv8w-hjr2 and fix it if it is affected.\n\nWhat it is: GHSA-8mf7-vv8w-hjr2 is a command injection vulnerability in openclaw, published on 3 Mar 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 GHSA-8mf7-vv8w-hjr2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.22\n- openclaw (npm): affected all versions; fixed in 2026.2.22\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-8mf7-vv8w-hjr2/ (Markdown: https://insights.sbomify.com/GHSA-8mf7-vv8w-hjr2/index.md)","id":"GHSA-8mf7-vv8w-hjr2","markdown":"https://insights.sbomify.com/GHSA-8mf7-vv8w-hjr2/index.md","name":"GHSA-8mf7-vv8w-hjr2","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenClaw npm library","requires_auth":"none","summary":"OpenClaw's generic fallback allowed interpreter binaries to execute inline payloads in allowlist mode, enabling code execution in misconfigured deployments.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nWhen `tools.exec.safeBins` contained a binary without an explicit safe-bin profile, OpenClaw used a permissive generic fallback profile. In allowlist mode, that could let interpreter-style binaries (for example `python3`, `node`, `ruby`) execute inline payloads via flags like `-c`.\n\nThis requires explicit operator configuration to add such binaries to `safeBins`, so impact is limited to non-default/misconfigured deployments.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Affected versions: `\u003c= 2026.2.21-2`\n- Patched in code: `\u003e= 2026.2.22` (planned next npm release)\n\n### Fix\n- Remove generic safe-bin fallback during allowlist evaluation.\n- Require explicit safe-bin profiles for `safeBins` entries.\n- Add configurable `tools.exec.safeBinProfiles` (global + per-agent) for safe custom binaries.\n- Update docs to clearly separate `safeBins` from command allowlist semantics.\n\n### Fix Commit(s)\n- `47c3f742b6c488be26dd7b9636dbbb8676089154`\n\n### Release Process Note\n`patched_versions` is pre-set to the planned next release (`\u003e= 2026.2.22`) so once that npm release is published, the advisory can be published directly without further metadata edits.\n\nOpenClaw thanks @tdjackey for reporting.","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's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode","id":"GHSA-8mf7-vv8w-hjr2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["2026.2.22"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-8mf7-vv8w-hjr2"},{"ecosystem":"npm","fixed":["2026.2.22"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-8mf7-vv8w-hjr2"}],"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":"OpenClaw's generic fallback allowed interpreter binaries to execute inline payloads in allowlist mode, enabling code execution in misconfigured deployments.","url":"https://insights.sbomify.com/GHSA-8mf7-vv8w-hjr2/"}