OpenClaw Package Vulnerability: Bypass of Shared-Secret Rate-Limit Budget

openclaw Updated 09 Apr 2026

Summary

09/04/2026

Disclosed on

LOW

Severity

Yes i

Fix available

Low

Severity

2.1

CVSS Score

GHSA-25wv-8phj-8p7r: Impact Concurrent async auth attempts can bypass the intended shared-secret rate-limit budget on Tailscale-capable paths. Affects openclaw versions < 2026.4.4. Fixed in 2026.4.4. 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 Browse

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.

Background

OpenClaw is a user-controlled local assistant designed to enhance user interaction with Tailscale-capable paths. It allows users to manage their authentication processes efficiently. However, it has been found to be vulnerable to concurrent asynchronous authentication attempts that can exploit its shared-secret rate-limit budget, potentially leading to unauthorized access.

Vulnerability Detail

The vulnerability arises from the handling of concurrent asynchronous shared-secret authentication attempts within OpenClaw. When multiple auth attempts are made simultaneously, they can race against the per-key rate-limit budget, effectively bypassing the intended security measures. This could allow an attacker to overwhelm the system and gain unauthorized access to resources, undermining the integrity of the authentication process.

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

This is the first release that contains the fix.

npm install openclaw@2026.4.4

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

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch as soon as possible to mitigate the risk.

Conclusion

The OpenClaw package has a vulnerability that allows concurrent authentication attempts to bypass security measures. Users are advised to update to the patched version 2026.4.4 to secure their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for openclaw →