What is the CVSS score of CVE-2026-27566?

CVE-2026-27566 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L. EPSS exploitation probability: 0.1%.

Which versions of Openclaw are affected by CVE-2026-27566?

OpenClaw contains a command execution vulnerability that allows low-privileged attackers to bypass security controls and execute unauthorized commands on affected systems.. A patch is available.

How to fix or mitigate CVE-2026-27566?

Within 24 hours: Inventory all systems running OpenClaw and assess exposure level; notify relevant team leads of vulnerability status. Within 7 days: Apply vendor patch to all non-production OpenClaw instances and conduct testing in staging environment to validate compatibility and functionality. Within 30 days: Complete patching of all production systems; document patch deployment and validate through security scanning or manual testing that allowlist controls are functioning correctly.

Openclaw CVE-2026-27566

EUVD-2026-13007 HIGH

OS Command Injection (CWE-78)

2026-03-19 VulnCheck

GHSA-jj82-76v6-933r

Command Injection Openclaw

7.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 19, 2026 - 01:30 euvd

EUVD-2026-13007

Analysis Generated

Mar 19, 2026 - 01:30 vuln.today

Patch released

Mar 19, 2026 - 01:30 nvd

Patch available

CVE Published

Mar 19, 2026 - 01:00 nvd

HIGH 7.1

DescriptionCVE.org

OpenClaw versions prior to 2026.2.22 contain an allowlist bypass vulnerability in system.run exec analysis that fails to unwrap env and shell-dispatch wrapper chains. Attackers can route execution through wrapper binaries like env bash to smuggle payloads that satisfy allowlist entries while executing non-allowlisted commands.

AnalysisAI

OpenClaw contains an allowlist bypass vulnerability in its system.run exec analysis that fails to properly unwrap wrapper binaries like env and bash. Attackers with low-level privileges can chain wrapper binaries to smuggle malicious commands that appear to satisfy allowlist entries while actually executing non-allowlisted payloads. A patch is available from the vendor, and the vulnerability was disclosed through VulnCheck advisory; no public proof-of-concept code or active exploitation (KEV listing) has been reported at this time.

Technical ContextAI

The vulnerability affects OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) versions prior to 2026.2.22 and is rooted in CWE-78 (Improper Neutralization of Special Elements used in an OS Command). The issue arises from insufficient validation in system.run's exec analysis logic, which implements an allowlist approach to restrict executable commands. However, the validation mechanism fails to recursively unwrap wrapper binary chains such as env bash -c or similar shell-dispatch constructs. This allows attackers to nest wrappers that individually pass allowlist checks but ultimately execute arbitrary commands when the chain is resolved by the operating system. The flaw represents a classic allowlist bypass through indirection, where the security control validates the outermost wrapper (e.g., /usr/bin/env) without inspecting the complete command execution chain that follows.

RemediationAI

Upgrade OpenClaw to version 2026.2.22 or later, which includes the fix implemented in commit 2b63592be57782c8946e521bc81286933f0f99c7 available at https://github.com/openclaw/openclaw/commit/2b63592be57782c8946e521bc81286933f0f99c7. Review the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-jj82-76v6-933r for complete upgrade instructions and any additional security recommendations. As a temporary mitigation until patching is complete, restrict access to system.run functionality to only highly trusted administrative users, implement additional input validation or sandboxing controls at the application layer, and monitor system logs for suspicious command execution patterns involving wrapper binaries like env, bash, or sh with unexpected argument chains. Consider implementing application-level allowlists that recursively parse and validate entire command chains rather than only the initial executable.