N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-43x4-g22p-3hrq

GHSA-43x4-g22p-3hrq: OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-43x4-g22p-3hrq

GHSA-43x4-g22p-3hrq:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.21	2026.2.21

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the fact that the sandbox browser container launched Chromium with the --no-sandbox flag by default, effectively disabling a critical security feature. The analysis of the provided commits confirms this. The commit e7eba01efc4c3c400e9cfd3ce3d661cbc788a631 directly addresses this by modifying scripts/sandbox-browser-entrypoint.sh. The script previously hardcoded the --no-sandbox argument. The patch removes this and makes it conditional based on the ALLOW_NO_SANDBOX environment variable. The function ensureSandboxBrowser in src/agents/sandbox/browser.ts is the TypeScript function responsible for creating and managing this container. While the most direct change is in the shell script, ensureSandboxBrowser is the function within the application's code that would be called to initiate this insecure behavior, making it a key function for developers to be aware of. The second commit, 1835dec2004fe7a62c6a7ba46b8485f124ec6199, introduces auditing functions like collectSandboxBrowserHashLabelFindings to detect containers that were created with the old, insecure configuration, further confirming the nature of the vulnerability and the fix.

Vulnerable functions

ensureSandboxBrowser

src/agents/sandbox/browser.ts

This function creates and configures the sandbox browser container. Prior to the fix, the container it created would launch Chromium with the `--no-sandbox` flag by default, disabling the browser's OS-level sandbox and weakening the security of the container.

scripts/sandbox-browser-entrypoint.sh

scripts/sandbox-browser-entrypoint.sh

This shell script is the entrypoint for the sandbox browser container. It was unconditionally adding the `--no-sandbox` argument when launching Chromium. This disabled the browser's sandbox, which is the root cause of the vulnerability. The patch makes this behavior opt-in via an environment variable.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

N/A

-

Basic Information

Basic Information

Concerned about an active attack path?

GHSA-43x4-g22p-3hrq: OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container

Summary

Affected Packages / Versions

Impact

Resolution

Fix Commit(s)

Release Process Note

GHSA-43x4-g22p-3hrq:

N/A

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

GHSA-43x4-g22p-3hrq: OpenClaw: Chrome --no-sandbox disabled OS-level browser sandbox in sandbox browser container

Summary

Affected Packages / Versions

Impact

Resolution

Fix Commit(s)

Release Process Note

N/A

N/A

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Technical Details

Basic Information

Basic Information

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI