Skip to main content

OpenClaw Nextcloud Talk CVE-2026-28474

CRITICAL
Incorrect Authorization (CWE-863)
2026-03-05 disclosure@vulncheck.com GHSA-r5h9-vjqc-hq3r
9.3
CVSS 4.0 · NVD
Share

Severity by source

NVD PRIMARY
9.3 CRITICAL
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

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

7
Source Code Evidence Fetched
May 06, 2026 - 14:58 vuln.today
Analysis Updated
May 06, 2026 - 14:58 vuln.today
v2 (cvss_changed)
Re-analysis Queued
May 06, 2026 - 14:52 vuln.today
cvss_changed
CVSS changed
May 06, 2026 - 14:52 NVD
9.8 (CRITICAL) 9.3 (CRITICAL)
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 12, 2026 - 22:06 vuln.today
CVE Published
Mar 05, 2026 - 22:16 nvd
CRITICAL 9.8

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

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-32064 HIGH POC
7.7 Mar 21

OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

CVE-2026-25474 HIGH POC
7.5 Feb 19

OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec

Share

CVE-2026-28474 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy