Skip to main content

Openclaw CVE-2026-27523

| EUVDEUVD-2026-12734 MEDIUM
Path Traversal (CWE-22)
2026-03-18 VulnCheck GHSA-m8v2-6wwh-r4gc
6.1
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
6.1 MEDIUM
AV:L/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:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

Lifecycle Timeline

4
EUVD ID Assigned
Mar 18, 2026 - 02:30 euvd
EUVD-2026-12734
Analysis Generated
Mar 18, 2026 - 02:30 vuln.today
Patch released
Mar 18, 2026 - 02:30 nvd
Patch available
CVE Published
Mar 18, 2026 - 01:34 nvd
MEDIUM 6.1

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 sandbox bind validation vulnerability allowing attackers to bypass allowed-root and blocked-path checks via symlinked parent directories with non-existent leaf paths. Attackers can craft bind source paths that appear within allowed roots but resolve outside sandbox boundaries once missing leaf components are created, weakening bind-source isolation enforcement.

AnalysisAI

OpenClaw versions prior to 2026.2.24 contain a sandbox bind validation bypass vulnerability that allows local attackers with low privileges to circumvent allowed-root and blocked-path security checks through symlinked parent directories combined with non-existent leaf paths. An attacker can craft bind source paths that appear to reside within permitted sandbox roots but resolve outside sandbox boundaries once missing path components are created, effectively weakening the sandbox's bind-source isolation enforcement. A patch is available from the vendor, and exploitation requires local access with standard user privileges, making this a practical threat in multi-tenant or shared-system environments.

Technical ContextAI

The vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory) stems from inadequate validation of filesystem paths during sandbox bind operations in OpenClaw. The issue involves symlink resolution and path canonicalization logic that fails to properly handle edge cases where intermediate path components do not yet exist. When a local attacker constructs a bind-source path containing a symlink in a parent directory coupled with a non-existent leaf component, the validation logic evaluates the path against allowed-root and blocked-path policies before the leaf is created. Once the missing component is subsequently created (either by the attacker or through normal system operations), the path resolves outside the intended sandbox boundaries. This is a classic time-of-check-time-of-use (TOCTOU) flaw combined with improper symlink handling. The affected product is OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), and the root cause involves the sandbox bind-mount validation subsystem's failure to perform proper path resolution and validation before enforcement.

RemediationAI

Upgrade OpenClaw to version 2026.2.24 or later immediately. The vendor has published a patch available in the public repository at https://github.com/openclaw/openclaw/commit/b5787e4abba0dcc6baf09051099f6773c1679ec1 which corrects the bind-path validation logic to properly handle symlinked parent directories and non-existent leaf paths. Until patching is possible, apply defense-in-depth measures: restrict local user access via strict user account policies and filesystem permissions, use mandatory access control (MAC) frameworks such as SELinux or AppArmor to enforce stricter bind-mount policies, monitor filesystem operations (particularly symlink creation) for suspicious patterns, and isolate OpenClaw workloads on dedicated, minimally-exposed systems where feasible. Verify the patch has been applied by checking the version string and reviewing relevant commit signatures.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-32064 HIGH POC
7.7 Mar 21

OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

CVE-2026-25474 HIGH POC
7.5 Feb 19

OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec

Share

CVE-2026-27523 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy