{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-qhrr-grqp-6x2g in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.22 or later.","what":"GHSA-qhrr-grqp-6x2g is a vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-qhrr-grqp-6x2g and fix it if it is affected.\n\nWhat it is: GHSA-qhrr-grqp-6x2g is a vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-qhrr-grqp-6x2g 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-qhrr-grqp-6x2g/ (Markdown: https://insights.sbomify.com/GHSA-qhrr-grqp-6x2g/index.md)","id":"GHSA-qhrr-grqp-6x2g","markdown":"https://insights.sbomify.com/GHSA-qhrr-grqp-6x2g/index.md","name":"GHSA-qhrr-grqp-6x2g","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":"low_privilege","summary":"Attackers can bypass exec allowlists in OpenClaw by shadowing safe binaries in trusted PATH directories, leading to arbitrary command execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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 `openclaw` allowlist mode, `tools.exec.safeBins` trusted PATH-derived directories for safe-bin resolution. A same-name binary placed in a trusted PATH directory could satisfy safe-bin checks and execute.\n\n### Impact\nThis is an allowlist bypass in exec policy that can lead to command execution in the OpenClaw runtime context when allowlist mode relies on safe bins and an attacker can influence trusted binary locations.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Vulnerable versions: `\u003c= 2026.2.21-2`\n- Patched versions: `\u003e= 2026.2.22` (planned next release)\n- Latest published npm version at triage time (2026-02-22): `2026.2.21-2`\n\n### Root Cause\n- Safe-bin trust accepted PATH-derived directories instead of explicit trusted directories.\n- Safe-bin execution used shell command tokens that could resolve to shadowed binaries.\n\n### Remediation\n- Stop trusting PATH-derived directories for safe-bin trust.\n- Add explicit `tools.exec.safeBinTrustedDirs` for opt-in extra trusted paths.\n- Pin safe-bin shell execution to resolved absolute executable paths.\n\n### Fix Commit(s)\n- `64b273a71cf0b2f2419c974832cede1fc2158729`\n\n### Release Process Note\n`patched_versions` is pre-set to the planned next release (`2026.2.22`). After npm release, this advisory is ready for publish without additional field 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 trusted PATH directories allowed binary shadowing in allowlist mode","id":"GHSA-qhrr-grqp-6x2g","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","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-qhrr-grqp-6x2g"},{"ecosystem":"npm","fixed":["2026.2.22"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-qhrr-grqp-6x2g"}],"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 bypass exec allowlists in OpenClaw by shadowing safe binaries in trusted PATH directories, leading to arbitrary command execution.","url":"https://insights.sbomify.com/GHSA-qhrr-grqp-6x2g/"}