{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-qcc4-p59m-p54m in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.26 or later.","what":"GHSA-qcc4-p59m-p54m is a path traversal vulnerability in openclaw, published on 12 Mar 2026."},"fix_prompt":"Check this codebase for GHSA-qcc4-p59m-p54m and fix it if it is affected.\n\nWhat it is: GHSA-qcc4-p59m-p54m is a path traversal vulnerability in openclaw, published on 12 Mar 2026. \nExploitation: There is no known exploitation of GHSA-qcc4-p59m-p54m in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.26\n- openclaw (npm): affected all versions; fixed in 2026.2.26\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-qcc4-p59m-p54m/ (Markdown: https://insights.sbomify.com/GHSA-qcc4-p59m-p54m/index.md)","id":"GHSA-qcc4-p59m-p54m","markdown":"https://insights.sbomify.com/GHSA-qcc4-p59m-p54m/index.md","name":"GHSA-qcc4-p59m-p54m","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"unknown","non_default_config":false,"product_category":"OpenClaw npm library","requires_auth":"none","summary":"An attacker can bypass sandbox write boundaries via dangling symlinks to modify files outside the workspace.","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\nA sandbox boundary-validation gap in symlink alias handling allowed certain workspace-only write paths to be treated as in-boundary even when they could resolve outside the workspace/sandbox root.\n\n### Affected Packages / Versions\n- Package: npm `openclaw`\n- Affected versions: `\u003c= 2026.2.25`\n- Latest published npm version included in affected range: `2026.2.25` (checked on February 26, 2026)\n- Patched version (pre-set for release): `2026.2.26`\n\n### Technical Details\nIn affected versions, dangling symlink hops could be accepted during boundary checks under missing-target conditions. For workspace-only write flows (including `apply_patch`), this could allow writes to resolve outside the configured workspace/sandbox boundary.\n\nThe fix resolves symlink targets through existing ancestors and fails closed when canonical resolution escapes the configured boundary.\n\n### Impact\n- Boundary-confined write operations could be redirected outside the configured workspace/sandbox root.\n- Primary impact is integrity of host-side files reachable from that path resolution.\n\n### Fix Commit(s)\n- `4fd29a35bb85a1898ebff518364c467058b50e14`\n\n### Release Process Note\n`patched_versions` is pre-set to the planned next release (`2026.2.26`) so once npm `2026.2.26` is published, the advisory can be published without further field edits.\n\nThanks @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: Sandbox dangling-symlink alias handling could bypass workspace-only write boundary","id":"GHSA-qcc4-p59m-p54m","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.26"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-qcc4-p59m-p54m"},{"ecosystem":"npm","fixed":["2026.2.26"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-qcc4-p59m-p54m"}],"products":null,"published":"2026-03-12","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":"An attacker can bypass sandbox write boundaries via dangling symlinks to modify files outside the workspace.","url":"https://insights.sbomify.com/GHSA-qcc4-p59m-p54m/"}