GHSA-43x4-g22p-3hrq
OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
Summary
Sandbox browser container launched Chromium with --no-sandbox by default, disabling Chromium's OS-level sandbox protections.
Affected Packages / Versions
- Package:
openclaw(npm ecosystem) - Latest published npm version at triage time (2026-02-21):
2026.2.19-2 - Affected range:
<= 2026.2.19-2 - Planned patched version for next release:
2026.2.21
Impact
When --no-sandbox is enabled by default, renderer compromise no longer requires a separate sandbox escape. This weakens container browser isolation and increases impact from renderer-side bugs.
Resolution
- Default
--no-sandboxremoved from sandbox browser entrypoint. - Explicit opt-in added via
OPENCLAW_BROWSER_NO_SANDBOX/CLAWDBOT_BROWSER_NO_SANDBOX. - Browser container hash migration + security audit checks added so stale containers are surfaced and can be recreated safely.
Fix Commit(s)
- e7eba01efc4c3c400e9cfd3ce3d661cbc788a631
- 1835dec2004fe7a62c6a7ba46b8485f124ec6199
Release Process Note
The advisory patched_versions field is pre-set to the planned next release (2026.2.21). After npm release publication, only advisory publish action should remain.
OpenClaw thanks @TerminalsandCoffee for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.21 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-43x4-g22p-3hrq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-43x4-g22p-3hrq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-43x4-g22p-3hrq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-43x4-g22p-3hrq in your dependencies?
O3 detects GHSA-43x4-g22p-3hrq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.