OpenClaw Webhooks SecretRef Vulnerability - Cached Secrets Allow Unauthorized Access

openclaw Updated 05 May 2026

Summary

05/05/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

6.0

CVSS Score

GHSA-q8ff-7ffm-m3r9: OpenClaw's Webhooks SecretRef route secret remains valid after rotation/reload. Affects openclaw versions < 2026.4.23. Fixed in 2026.4.23. 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 an open-source tool designed for managing webhooks, enabling seamless integration between various services. It utilizes SecretRef values to secure webhook routes, ensuring that only authorized requests can trigger specific actions. However, a flaw in its caching mechanism has led to vulnerabilities in secret management, allowing previously valid secrets to remain effective even after being rotated.

Vulnerability Detail

The vulnerability arises from OpenClaw's handling of webhook route secrets backed by SecretRef values. When an operator rotates the underlying secret and executes the 'openclaw secrets reload' command, the system may still allow the previously resolved webhook secret to authenticate requests until the plugin or gateway is restarted. This flaw can lead to unauthorized access, as an attacker with a valid secret can continue to invoke webhook tasks despite the secret being rotated.

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

This is the first release that contains the fix.

npm install openclaw@2026.4.23

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

Workaround

As a temporary workaround, consider restarting the OpenClaw plugin or gateway after rotating the webhook secrets. This will invalidate any previously cached secrets and ensure that only the new secret is accepted for authentication.

Conclusion

The OpenClaw vulnerability related to cached webhook secrets poses a significant risk by allowing unauthorized access even after secret rotation. It is crucial for users to update to the latest version to mitigate this risk and ensure secure webhook management.

See every vulnerability recorded for openclaw →