https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T16:01:28.062757+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32046 BREW-openclaw-cli-CVE-2026-32046 — OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container 2026-10-03T16:01:28.067547+00:00

Affected: Homebrew: openclaw-cli

## 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.

 https://cve.radiocsirt.org/vuln/cnvd-2026-16049 cnvd-2026-16049 2026-10-03T16:01:28.067613+00:00 cnvd-2026-16049 https://cve.radiocsirt.org/vuln/euvd-2026-329442 EUVD-2026-329442 2026-10-03T16:01:28.067631+00:00 EUVD-2026-329442 https://cve.radiocsirt.org/vuln/fkie_cve-2026-32046 fkie_cve-2026-32046 2026-10-03T16:01:28.067643+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-43x4-g22p-3hrq GHSA-43x4-g22p-3hrq — OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container 2026-10-03T16:01:28.067665+00:00

Affected: npm: openclaw

## 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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0472 WID-SEC-W-2026-0472 — OpenClaw: Mehrere Schwachstellen 2026-10-03T16:01:28.067695+00:00

Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, sich erhöhte Berechtigungen zu verschaffen, Daten zu manipulieren, einen Denial-of-Service-Zustand auszulösen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.