CVE-2026-28474: OpenClaw nextcloud-talk · Incorrect Authorization
Affects OpenClaw nextcloud-talkSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 2026.2.6 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade OpenClaw nextcloud-talk to 2026.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenClawnextcloud-talk | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-28474, organizations should immediately upgrade OpenClaw's Nextcloud Talk plugin to version 2026.2.6 or later, where the authorization logic no longer relies on the mutable display name field. Until patching is possible, administrators should consider implementing additional access controls at the network or application layer, such as IP whitelisting or VPN requirements, to restrict access to Nextcloud Talk. Monitoring logs for suspicious display name changes and unauthorized access attempts can help detect exploitation attempts. Organizations should also educate users about the risk of display name impersonation and enforce policies to limit display name changes if supported. Reviewing and strengthening allowlist validation mechanisms to use immutable, unique user identifiers rather than mutable attributes is critical for long-term security. Finally, applying defense-in-depth strategies, including multi-factor authentication and encrypted communication channels, can reduce overall risk.
Description
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.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-r5h9-vjqc-hq3r (opens in a new tab)
- github.com/openclaw/openclaw/commit/6b4b6049b47c3329a7014509594647826669892d (opens in a new tab)
- vulncheck.com/advisories/openclaw-nextcloud-talk-allowlist-bypass-via-actorname-display-name-spoofing (opens in a new tab)