{"answers":{"affected":"2 open source packages ship an affected version, including openclaw.","exploited":"There is no known exploitation of GHSA-w7j5-j98m-w679 in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.21 or later.","what":"GHSA-w7j5-j98m-w679 is a vulnerability in openclaw, published on 3 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-w7j5-j98m-w679 and fix it if it is affected.\n\nWhat it is: GHSA-w7j5-j98m-w679 is a vulnerability in openclaw, published on 3 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-w7j5-j98m-w679 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.21\n- openclaw (npm): affected all versions; fixed in 2026.2.21\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-w7j5-j98m-w679/ (Markdown: https://insights.sbomify.com/GHSA-w7j5-j98m-w679/index.md)","id":"GHSA-w7j5-j98m-w679","markdown":"https://insights.sbomify.com/GHSA-w7j5-j98m-w679/index.md","name":"GHSA-w7j5-j98m-w679","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker test images","requires_auth":"none","summary":"OpenClaw test Dockerfiles run as root, allowing attackers to gain root privileges inside the container if a process is compromised.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Three Dockerfiles in scripts/docker/ and scripts/e2e/ lack a USER directive, meaning all processes run as uid 0 (root). If any process is compromised, the attacker has root inside the container, making container breakout significantly easier.\n**Partial fix (2026-02-08):** Commit 28e1a65e added USER sandbox to Dockerfile.sandbox and Dockerfile.sandbox-browser. The E2E/test Dockerfiles listed below remain unpatched.\n\n**Affected components:**\n- scripts/e2e/Dockerfile\n- scripts/e2e/Dockerfile.qr-import\n- scripts/docker/install-sh-e2e/Dockerfile\n- scripts/docker/install-sh-nonroot/Dockerfile (runs as app but with NOPASSWD sudo — see related advisory)\n\n**Technical Reproduction:**\n1. Open each Dockerfile listed above and search for a USER directive — none found.\n2. Run any of these containers: docker run --rm -it \u003cimage\u003e id\n3. Observe: returns uid=0(root).\n\n**Demonstrated Impact:**\n- Root inside the container enables kernel exploit attempts, volume mount abuse, and privileged syscall access.\n- Test images share the same base (node:22-bookworm) as production, creating risk of accidental deployment of root-running images.\n\n**Environment:** Base images node:22-bookworm and node:22-bookworm-slim default to root. Dockerfile.sandbox and Dockerfile.sandbox-browser were remediated in commit 28e1a65e; only the E2E/test images listed above remain affected.\n\n**Remediation:** Add a USER directive before CMD/ENTRYPOINT in each remaining Dockerfile:\n  RUN useradd --create-home --shell /bin/bash appuser\n  USER appuser","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 has multiple E2E/test Dockerfiles that run all processes as root","id":"GHSA-w7j5-j98m-w679","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"misconfiguration","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["2026.2.21"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-w7j5-j98m-w679"},{"ecosystem":"npm","fixed":["2026.2.21"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-w7j5-j98m-w679"}],"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 test Dockerfiles run as root, allowing attackers to gain root privileges inside the container if a process is compromised.","url":"https://insights.sbomify.com/GHSA-w7j5-j98m-w679/"}