Webhook Path Route Replacement Vulnerability in OpenClaw

openclaw Updated 10 Apr 2026

Summary

10/04/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

4.8

CVSS Score

GHSA-g8mc-c5f2-mqg7: Duplicate Advisory: OpenClaw Bypasses DM Policy Separation via Synology Chat Webhook Path Collision. Affects openclaw versions < 2026.3.22. Fixed in 2026.3.22. 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 application designed for managing multi-account configurations and integrations, particularly with services like Synology Chat. It allows users to set up webhooks for various functionalities. However, a vulnerability exists in its webhook path handling, which can lead to security issues if not addressed.

Vulnerability Detail

The vulnerability in OpenClaw, identified as a webhook path route replacement issue, allows attackers to exploit shared webhook paths across multiple accounts. This can lead to the bypassing of direct message (DM) access control policies, enabling unauthorized access to sensitive information. The issue arises from the improper handling of inherited or duplicate webhook paths, which can collapse multi-account configurations, leading to potential data leaks and unauthorized actions.

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

This is the first release that contains the fix.

npm install openclaw@2026.3.22

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

Workaround

As a temporary workaround, consider isolating webhook paths for different accounts to prevent path collisions. This can involve renaming webhook paths or using unique identifiers to ensure that each account's webhook is distinct.

Conclusion

The webhook path route replacement vulnerability in OpenClaw poses a significant risk to users managing multi-account configurations. It is crucial to update to the patched version to mitigate this risk. Additionally, using workarounds can help secure your application until an update can be applied.

See every vulnerability recorded for openclaw →