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

EUVD-2026-14561 has a CVSS 3.1 base score of 5.8 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L.

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

Organizations using OpenClaw before 2026.3.2 should be aware of moderate risk from CVE-2026-28483 rated CVSS 5.8. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate EUVD-2026-14561?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Openclaw EUVD-2026-14561

| CVE-2026-28483 MEDIUM

Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

2026-03-23 VulnCheck

Information Disclosure Openclaw

5.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 23, 2026 - 22:00 euvd

EUVD-2026-14561

Analysis Generated

Mar 23, 2026 - 22:00 vuln.today

Patch released

Mar 23, 2026 - 22:00 nvd

Patch available

CVE Published

Mar 23, 2026 - 21:36 nvd

MEDIUM 5.8

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.2.

DescriptionCVE.org

OpenClaw before 2026.3.2 contains a race condition vulnerability in ZIP extraction that allows local attackers to write files outside the intended destination directory via parent-directory symlink rebind between path validation and file write operations. Attackers can exploit the gap between validation and truncate operations in src/infra/archive.ts to redirect writes outside the extraction root by manipulating parent directory symlinks.

AnalysisAI

OpenClaw before version 2026.3.2 contains a race condition vulnerability in its ZIP extraction functionality that allows local attackers with limited privileges to write arbitrary files outside the intended extraction directory. The vulnerability exploits a time-of-check-time-of-use (TOCTOU) gap in src/infra/archive.ts where an attacker can rebind parent directory symlinks between path validation and file write operations, enabling directory traversal and potential code execution. A patch is available from the vendor, and this vulnerability requires local access with user-level privileges to exploit, making it a moderate-severity concern for systems where untrusted users can extract archives.

Technical ContextAI

OpenClaw (cpe:2.3:a:openclaw:openclaw) is an archive extraction utility where the vulnerable code resides in src/infra/archive.ts. The root cause is classified as CWE-367 (Time-of-check-time-of-use race condition), which describes a class of vulnerabilities where the time gap between security validation and resource use allows attackers to modify security-relevant conditions. In this case, the validation step checks whether extracted file paths are within the intended extraction root directory, but before the file is actually written, an attacker can modify parent directory symlinks to redirect the write operation outside the extraction boundary. This is a classic symlink-based TOCTOU vulnerability common in archive extraction tools that do not properly handle or reject symbolic links during extraction.

RemediationAI

Immediately upgrade OpenClaw to version 2026.3.2 or later, which includes the fix from commit 7dac9b05dd9d38dd3929637f26fa356fd8bdd107 available at https://github.com/openclaw/openclaw/commit/7dac9b05dd9d38dd3929637f26fa356fd8bdd107. The patch addresses the race condition by implementing proper symlink handling and atomic validation-to-write operations in src/infra/archive.ts. As a temporary mitigation before patching, restrict archive extraction operations to trusted users only, disable symbolic link support in ZIP extraction if the application allows it, and consider running archive extraction in a sandboxed or containerized environment with restricted filesystem access to limit the scope of potential file writes. Monitor system logs for suspicious symlink creation or file write attempts outside expected directories.