Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Trusted input validation
|
| Impact | The CVSS score of 5.9 (Medium) reflects a credible but constrained threat. The attack vector is network-based (AV:N) with high complexity (AC:H), requiring authentication (PR:L), and resulting in high confidentiality impact (C:H) and low integrity impact (I:L). The AC:H modifier significantly lowers urgency-successful exploitation requires the attacker to manipulate username resolution timing and conditions, suggesting environmental preconditions or race conditions may be necessary. EPSS data is not provided, but the requirement for prior authentication (PR:L) and the complexity of username rebinding coordination substantially reduce the likelihood of opportunistic exploitation compared to unauthenticated remote code execution vulnerabilities. Patch availability from the vendor further de-risks this issue for organizations that can apply updates. The lack of known public exploit code or CISA KEV confirmation indicates this is not an imminent mass-exploitation threat, though the technical impact (redirecting sensitive communication) makes timely patching important for organizations using OpenClaw webhooks. This is a genuine but lower-urgency priority compared to high-impact, low-complexity vulnerabilities. |
| Exploit ScenarioDerived | An authenticated attacker with access to OpenClaw monitors a webhook integration (e.g., a support ticketing system sending replies into OpenClaw chat). When a webhook event arrives containing a username-based recipient binding for user alice, the attacker changes their own username to alice or exploits a username collision/race condition at the moment the webhook is processed. The webhook reply-which may contain sensitive information like password reset links or private support information-is delivered to the attacker instead of alice. AC:H suggests this timing must align with specific conditions, but in organizations with frequent webhook traffic or predictable timing, successful exploitation is feasible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 10, 2026
OpenClaw before version 2026.3.22 allows authenticated attackers to redirect webhook-triggered chat replies to unintended users by exploiting username-based recipient binding instead of stable numeric identifiers. An attacker with valid credentials can manipulate username changes to rebind webhook replies intended for one user to a different user, compromising message confidentiality and integrity. No public exploit code or active CISA exploitation data is available, but the vulnerability is confirmed patched by the vendor.
RemediationAI
Upgrade OpenClaw to version 2026.3.22 or later. The vendor has released a patched version addressing the username-based recipient binding flaw; two upstream commits (630f1479c44f78484dfa21bb407cbe6f171dac87 and 7ade3553b74ee3f461c4acd216653d5ba411f455) implement the fix, moving the system to stable numeric user identifiers for webhook recipient binding. Organizations unable to upgrade immediately should review webhook integration configurations and restrict webhook permissions to trusted external services only. Consult the OpenClaw GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-wv46-v6xc-2qhf and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-webhook-reply-rebinding-via-username-resolution-in-synology-chat for additional mitigation guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exploits a fundamental design flaw in OpenClaw's webhook reply delivery mechanism. Rather than using immutable numeric user identifiers to bind webhook events to their intended recipients, the system relies on usernames-which are mutable and can be changed by users or administrators. When a webhook event is triggered (e.g., an external system replies to a chat message), the system attempts to deliver that reply to the user specified by the webhook metadata. However, if the webhook metadata contains a username instead of a stable user ID, an attacker can change their own username or manipulate username resolution to match the target user's name at delivery time, causing the reply to be routed to the attacker instead of the intended recipient. This is rooted in CWE-807 (Reliance on Untrusted Inputs in a Security Decision), where mutable user attributes are incorrectly trusted for security-critical operations. The affected OpenClaw product is a chat integration system (often deployed via Synology Chat), and this vulnerability specifically impacts the webhook integration subsystem that bridges external services with internal chat delivery.
Know when Openclaw gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
OpenClaw before 2026.3.22 contains a webhook reply delivery vulnerability that allows attackers to rebind chat replies to unintended users by exploiting mutable username matching instead of stable numeric user identifiers. Attackers can manipulate username changes to redirect webhook-triggered replies to different users, bypassing the intended recipient binding recorded in webhook events.
Blast Radius
ecosystem impact- 5 npm packages depend on openclaw (5 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.3.22.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in OpenClaw Multiple Authorization and Privilege Escalation
View all 29Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a
Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
EUVD-2026-21486
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB