OpenClaw Nextcloud Talk
CVE-2026-28474
CRITICAL
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
7DescriptionCVE.org
OpenClaw's Nextcloud Talk plugin versions prior to 2026.2.6 accept equality matching on the mutable actor.name display name field for allowlist validation, allowing attackers to bypass DM and room allowlists. An attacker can change their Nextcloud display name to match an allowlisted user ID and gain unauthorized access to restricted conversations.
AnalysisAI
Authentication bypass in OpenClaw's Nextcloud Talk plugin versions ≤2026.2.2 allows remote unauthenticated attackers to bypass DM and room allowlists by spoofing display names. Attackers can change their Nextcloud display name to match an allowlisted user ID, gaining unauthorized access to restricted conversations without authentication. EPSS score is low (0.05%, 16th percentile), indicating low observed exploitation probability. No active exploitation confirmed; vulnerability was responsibly disclosed by AISLE Research Team and patched in version 2026.2.6.
Technical ContextAI
The vulnerability stems from improper authorization (CWE-863) in the @openclaw/nextcloud-talk npm package. Nextcloud Talk webhooks provide two actor identifiers: actor.id (stable, immutable user ID) and actor.name (mutable display name controlled by the user). The flawed implementation performed allowlist validation using string equality matching against both fields. Because actor.name is user-controlled and can be changed at will through Nextcloud's profile settings, attackers could set their display name to match any allowlisted user ID string. The policy.ts module's resolveNextcloudTalkAllowlistMatch function treated display names as trusted identifiers equivalent to actual user IDs. The fix removes all senderName parameters from allowlist validation logic, ensuring only the immutable actor.id field is checked. This is a classic confused deputy problem where the system trusted attacker-controllable input (display name) as if it were a verified identity claim (user ID).
RemediationAI
Upgrade the @openclaw/nextcloud-talk package to version 2026.2.6 or later via npm (npm install @openclaw/nextcloud-talk@latest). The patch commit 6b4b6049b47c3329a7014509594647826669892d removes display name matching from allowlist validation logic, ensuring only immutable actor.id fields are checked. Organizations unable to upgrade immediately should remove allowlist-based access controls and temporarily switch to open access or alternative authentication mechanisms until patching is complete, accepting the trade-off of reduced granular access control. Do not attempt to block specific display names as a workaround-the vulnerability is architectural and cannot be mitigated through configuration. Review conversation access logs for the period between January 20, 2026 (vulnerability introduction) and patch deployment to identify potential unauthorized access; look for actor.name values matching allowlisted user IDs where actor.id differs. Vendor advisory: https://github.com/openclaw/openclaw/security/advisories/GHSA-r5h9-vjqc-hq3r. VulnCheck advisory: https://www.vulncheck.com/advisories/openclaw-nextcloud-talk-allowlist-bypass-via-actorname-display-name-spoofing.
Auth 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
OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all
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
OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low
OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
GHSA-r5h9-vjqc-hq3r