Symlink Traversal Vulnerability in OpenClaw: Incomplete Fix for CVE-2026-32013

openclaw Updated 18 Apr 2026

Summary

10/04/2026
MODERATE
No i
Moderate
7.1

GHSA-pmf3-2q63-jmp6: Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-7xr2-q9vf-x4r5. Affects openclaw versions < 2026.2.22. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenClaw is an open-source project designed for managing and automating various tasks through agents. It leverages Node.js and npm for package management, providing users with a flexible framework for creating and updating agents. However, a significant vulnerability was discovered in versions up to 2026.2.22, where symlink traversal could allow unauthorized access and remote code execution.

Vulnerability Detail

The vulnerability arises from the use of fs.appendFile on the IDENTITY.md file without proper symlink containment checks in the agents.create and agents.update handlers. This flaw allows attackers with workspace access to create symlinks that can append malicious content to arbitrary files. The consequences include potential remote code execution through crontab injection or unauthorized SSH key manipulation, posing a serious security risk.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, update OpenClaw to a patched version beyond 2026.2.22. You can do this by running the following command in your terminal: npm update openclaw. Ensure that you check the release notes for any additional changes that may affect your application.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, restrict workspace access to trusted users only and monitor file permissions closely to prevent unauthorized symlink creation. Additionally, consider implementing symlink containment checks in your application code to mitigate the risk until an official patch is applied.

Conclusion

The symlink traversal vulnerability in OpenClaw poses a significant risk to users, allowing attackers to exploit the system for unauthorized access and remote code execution. It is crucial to update to the latest version to mitigate this risk and implement additional security measures as needed.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 7.1, indicating a moderate severity level.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

The vulnerability could lead to unauthorized access, remote code execution, and manipulation of critical files, which can compromise the security of your application.

Yes, a patched version of OpenClaw is available. Ensure you update to a version beyond 2026.2.22 to mitigate the risk.

If you cannot update immediately, restrict access to your workspace and monitor file permissions closely to prevent unauthorized symlink creation.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, update OpenClaw to a patched version beyond 2026.2.22. You can do this by running the following command in your terminal: npm update openclaw. Ensure that you check the release notes for any additional changes that may affect your application.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.