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

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

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

CVE-2026-32009 presents moderate security risk rated CVSS 5.7. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2026-32009?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Openclaw CVE-2026-32009

MEDIUM

Untrusted Search Path (CWE-426)

2026-03-19 disclosure@vulncheck.com

GHSA-5gj7-jf77-q2q2

Authentication Bypass Openclaw

5.7

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.7 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 19, 2026 - 22:30 vuln.today

CVE Published

Mar 19, 2026 - 22:16 nvd

MEDIUM 5.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.24.

DescriptionCVE.org

OpenClaw versions prior to 2026.2.24 contain a policy bypass vulnerability in the safeBins allowlist evaluation that trusts static default directories including writable package-manager paths like /opt/homebrew/bin and /usr/local/bin. An attacker with write access to these trusted directories can place a malicious binary with the same name as an allowed executable to achieve arbitrary command execution within the OpenClaw runtime context.

AnalysisAI

Arbitrary command execution in OpenClaw prior to version 2026.2.24 results from improper validation of binaries in package manager directories that are included in the safeBins allowlist. An attacker with write access to trusted paths such as /opt/homebrew/bin or /usr/local/bin can plant a malicious binary to achieve code execution within the OpenClaw runtime. No patch is currently available.

Technical ContextAI

The vulnerability stems from CWE-426 (Untrusted Search Path) and represents a fundamental flaw in OpenClaw's safeBins allowlist evaluation logic. The application maintains a list of allowed executables that can be invoked within its runtime context, but the implementation incorrectly trusts static default directories without validating the integrity or origin of binaries within those paths. Package-manager directories like /opt/homebrew/bin (macOS Homebrew) and /usr/local/bin are commonly writable by non-root users or package managers themselves, creating an exploitable trust boundary. The safeBins mechanism is intended to prevent arbitrary command execution, but by failing to perform path canonicalization, ownership verification, or runtime integrity checks, it becomes a false security boundary. This is a classic privilege escalation vector in Unix-like systems where the PATH environment variable or hardcoded search paths can be poisoned by a user with directory write permissions.

RemediationAI

Upgrade OpenClaw to version 2026.2.24 or later immediately. The patch addresses the safeBins allowlist evaluation logic to remove trust in static default writable directories and implement path canonicalization and ownership verification. Until patching is possible, restrict write permissions on trusted binary directories (/opt/homebrew/bin, /usr/local/bin) to root or the OpenClaw service account only, and run OpenClaw with minimal privileges in a sandboxed or containerized environment to limit the impact of potential binary hijacking. Additionally, monitor these directories for unexpected binary modifications using file integrity monitoring (FIM) tools such as Auditd, Aide, or Osquery. Review and audit any CI/CD pipelines or automation that may grant users write access to system binary paths. See the vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-5gj7-jf77-q2q2 for detailed remediation guidance.