What is the CVSS score of EUVD-2026-12732?

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

Which versions of Openclaw are affected by EUVD-2026-12732?

CVE-2026-27522 presents notable security risk, a path traversal vulnerability rated CVSS 6.5. This could allow unauthorized file access.. A patch is available.

How to fix or mitigate EUVD-2026-12732?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Review file handling controls.

Openclaw EUVD-2026-12732

| CVE-2026-27522 MEDIUM

Path Traversal (CWE-22)

2026-03-18 VulnCheck

GHSA-fqcm-97m6-w7rm

Path Traversal Openclaw

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

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:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 18, 2026 - 02:30 euvd

EUVD-2026-12732

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

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 local media root bypass vulnerability in sendAttachment and setGroupIcon message actions when sandboxRoot is unset. Attackers can hydrate media from local absolute paths to read arbitrary host files accessible by the runtime user.

AnalysisAI

OpenClaw versions prior to 2026.2.24 contain a local media root bypass vulnerability that allows authenticated attackers to read arbitrary files from the host system through the sendAttachment and setGroupIcon message actions when sandboxRoot configuration is unset. An attacker with valid credentials can exploit path traversal to hydrate media from absolute file paths, gaining unauthorized access to sensitive files accessible by the OpenClaw runtime user. A patch is available from the vendor, and this vulnerability has been tracked in the ENISA EUVD database (EUVD-2026-12732) with confirmed GitHub security advisory and commit-level patch information.

Technical ContextAI

The vulnerability exists in OpenClaw's message handling functionality, specifically in the sendAttachment and setGroupIcon actions that process media file references. The root cause is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), which represents a path traversal weakness. When the sandboxRoot configuration parameter is not set (remains unset), the application fails to properly validate and restrict media file paths to an intended sandbox directory, allowing attackers to supply absolute file paths that bypass directory restrictions. This affects all versions of OpenClaw prior to 2026.2.24, as confirmed by the CPE string cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:* which matches all affected versions in that range.

RemediationAI

Upgrade OpenClaw to version 2026.2.24 or later immediately, using the patch provided by the vendor at https://github.com/openclaw/openclaw/commit/270ab03e379f9653e15f7033c9830399b66b7e51 or the full advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-fqcm-97m6-w7rm. Ensure the sandboxRoot configuration parameter is explicitly set to a restricted directory in all OpenClaw deployments to prevent future exploitation even if the code-level fix is incomplete. As a temporary mitigation for instances that cannot be immediately patched, restrict network access to OpenClaw to trusted internal networks only, revoke unnecessary user accounts to reduce the authenticated attack surface, and monitor for suspicious file access patterns in application logs (particularly sendAttachment and setGroupIcon calls with absolute paths). Additionally, implement file access controls at the OS level to ensure the OpenClaw runtime user has minimal necessary permissions.