Arbitrary File Read Vulnerability in OpenClaw Package

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
6.9

GHSA-56pc-6hvp-4gv4: OpenClaw vulnerable to arbitrary file read via $include directive. Affects openclaw versions < 2026.2.17. Fixed in 2026.2.17. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenClaw is an open-source package designed for managing configurations and includes directives for file inclusion. It allows users to include external files within its configuration, enhancing flexibility. However, this functionality can be exploited if not properly secured, leading to potential unauthorized access to sensitive files on the server.

Vulnerability Detail

The vulnerability arises from a path traversal issue in the configuration's $include directive, which allows attackers to read arbitrary files outside the designated config directory. If an attacker can modify the OpenClaw configuration, they can set the $include directive to absolute paths or use traversal paths to escape the config directory. This can lead to exposure of sensitive information, such as API keys and private configuration data, depending on the file permissions of the OpenClaw process user.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.17

This is the first release that contains the fix.

npm install openclaw@2026.2.17

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, ensure that the OpenClaw configuration is not modifiable by untrusted users. Additionally, avoid using symlinks within the config directory that could point to external files.

Conclusion

The OpenClaw package has a significant vulnerability that allows for arbitrary file reads due to a path traversal issue in the $include directive. Users are advised to update to version 2026.2.17 or later to secure their applications. For ongoing monitoring, consider using Vulert to stay informed about vulnerabilities.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability is a path traversal issue that allows arbitrary file reads via the $include directive in the configuration.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json.

Exploiting this vulnerability can lead to unauthorized access to sensitive files, including API keys and private configuration data, depending on the permissions of the OpenClaw process user.

Yes, a patched version (2026.2.17) is available. Users should update to this version to mitigate the vulnerability.

If immediate updating is not possible, restrict access to the OpenClaw configuration and avoid using symlinks that could lead to external file access.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.17

This is the first release that contains the fix.

npm install openclaw@2026.2.17

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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.