https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:13:18 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32046 <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-32046 https://vulnerability.circl.lu/vuln/ghsa-43x4-g22p-3hrq <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary Sandbox browser container launched Chromium with `--no-sandbox` by default, disabling Chromium&#39;s OS-level sandbox protections.</p> <p>## Affected Packages / Versions - Package: `openclaw` (npm ecosystem) - Latest published npm version at triage time (2026-02-21): `2026.2.19-2` - Affected range: `&lt;= 2026.2.19-2` - Planned patched version for next release: `2026.2.21`</p> <p>## 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.</p> <p>## 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.</p> <p>## Fix Commit(s) - e7eba01efc4c3c400e9cfd3ce3d661cbc788a631 - 1835dec2004fe7a62c6a7ba46b8485f124ec6199</p> <p>## 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.</p> <p>OpenClaw thanks @TerminalsandCoffee for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary Sandbox browser container launched Chromium with `--no-sandbox` by default, disabling Chromium&#39;s OS-level sandbox protections.</p> <p>## Affected Packages / Versions - Package: `openclaw` (npm ecosystem) - Latest published npm version at triage time (2026-02-21): `2026.2.19-2` - Affected range: `&lt;= 2026.2.19-2` - Planned patched version for next release: `2026.2.21`</p> <p>## 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.</p> <p>## 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.</p> <p>## Fix Commit(s) - e7eba01efc4c3c400e9cfd3ce3d661cbc788a631 - 1835dec2004fe7a62c6a7ba46b8485f124ec6199</p> <p>## 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.</p> <p>OpenClaw thanks @TerminalsandCoffee for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-43x4-g22p-3hrq