Local File Access Vulnerability in OpenClaw Package Allows Unauthorized File Reading

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
6.5

GHSA-45cg-2683-gfmq: Impact assertBrowserNavigationAllowed() validated only http:/https: network targets but implicitly allowed other schemes. Affects openclaw versions < 2026.2.21. Fixed in 2026.2.21. 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 a browser tool designed to facilitate interactions with web applications through a secure gateway. It provides features for authenticated users to navigate and manipulate browser sessions. However, a recent vulnerability has been identified that allows authenticated users to access local files on the server, posing a significant security risk.

Vulnerability Detail

The vulnerability arises from the assertBrowserNavigationAllowed() function, which only validates http: and https: URLs but inadvertently permits other URL schemes, such as file://. This oversight allows authenticated users to navigate to local file paths and read sensitive information, such as configuration files or secrets, through browser snapshot and extraction methods. The potential ramifications include unauthorized access to sensitive data, leading to data breaches or further exploitation of the system.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.21

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

Workaround

As a temporary workaround, you can implement additional validation in your application to reject unsupported navigation schemes. Ensure that only safe non-network URLs are allowed. For example, you can modify the navigation guard logic to include checks against file:, data:, and javascript: schemes.

Conclusion

The OpenClaw package has a vulnerability that allows authenticated users to access local files through improper URL validation. It is crucial to update to the patched version 2026.2.21 to mitigate this risk. Implementing additional validation can serve as a temporary workaround while ensuring the security of sensitive data.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

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

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

An attacker can access any local files that are readable by the OpenClaw process user, including sensitive configuration files and secrets.

Yes, you can implement additional validation to reject unsupported URL schemes as a temporary measure until you can update the package.

If immediate updates are not possible, ensure that your application has strict input validation and consider restricting access to the browser tool until the vulnerability is resolved.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.21

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