{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-3jx4-q2m7-r496 in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.25 or later.","what":"GHSA-3jx4-q2m7-r496 is a path traversal vulnerability in openclaw, published on 4 Mar 2026."},"fix_prompt":"Check this codebase for GHSA-3jx4-q2m7-r496 and fix it if it is affected.\n\nWhat it is: GHSA-3jx4-q2m7-r496 is a path traversal vulnerability in openclaw, published on 4 Mar 2026. \nExploitation: There is no known exploitation of GHSA-3jx4-q2m7-r496 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.25\n- openclaw (npm): affected all versions; fixed in 2026.2.25\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-3jx4-q2m7-r496/ (Markdown: https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/index.md)","id":"GHSA-3jx4-q2m7-r496","markdown":"https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/index.md","name":"GHSA-3jx4-q2m7-r496","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"unknown","non_default_config":true,"product_category":"OpenClaw npm library","requires_auth":"none","summary":"Attackers can read or modify files outside the workspace via hardlink aliases in OpenClaw when workspace-only restrictions are enabled.","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 certain workspace-restricted configurations, OpenClaw could follow hardlink aliases inside the workspace that reference files outside the workspace boundary.\n\nBy default, `tools.fs.workspaceOnly` is off. This primarily affects deployments that intentionally enable workspace-only filesystem restrictions (and workspace-only `apply_patch` checks).\n\n### Impact\n- Confidentiality: out-of-workspace files could be read through in-workspace hardlink aliases.\n- Integrity: out-of-workspace files could be modified through in-workspace hardlink aliases.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Latest published version at triage time: `2026.2.24`\n- Affected range: `\u003c= 2026.2.24`\n- Planned patched version: `2026.2.25`\n\n### Fix Commit(s)\n- `04d91d0319b82fd4de91ed05e9fc5219ff2ab64e` (main)\n\n### Remediation\nOpenClaw now rejects hardlinked final-file aliases during workspace boundary validation for:\n- workspace-only path checks (`read` / `write` / `edit`)\n- workspace-only `apply_patch` read/write paths\n- sandbox mount-root path-safety checks\n\nRegression tests were added for `apply_patch`, workspace fs tools, and sandbox fs bridge hardlink alias escapes.\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: Hardlink alias checks could bypass workspace-only file boundaries in specific configurations","id":"GHSA-3jx4-q2m7-r496","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.25"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-3jx4-q2m7-r496"},{"ecosystem":"npm","fixed":["2026.2.25"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-3jx4-q2m7-r496"}],"products":null,"published":"2026-03-04","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 or modify files outside the workspace via hardlink aliases in OpenClaw when workspace-only restrictions are enabled.","url":"https://insights.sbomify.com/GHSA-3jx4-q2m7-r496/"}