요약
- CVE-2026-32046은(는) openclaw (openclaw), openclaw에 영향을 주는 심각 (CVSS 9.8) 취약점입니다.
- 향후 30일 내 악용 확률(EPSS): 0.30%, 전체 취약점의 22.6%보다 높음.
- 조치: 2026.2.21 이상으로 업데이트하세요.
| Package | Affected versions | Patched versions |
|---|
| openclaw | < 2026.2.21
| 2026.2.21
|
| openclaw npm | < 2026.2.21
| 2026.2.21
|
Description
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-sandbox removed 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.
NVD description
OpenClaw versions prior to 2026.2.21 contain an improper sandbox configuration vulnerability that allows attackers to execute arbitrary code by exploiting renderer-side vulnerabilities without requiring a sandbox escape. Attackers can leverage the disabled OS-level sandbox protections in the Chromium browser container to achieve code execution on the host system.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free