Nextcloud Talk allowlist bypass via actor.name display name spoofing
CVE-2026-28474 · GHSA-r5h9-vjqc-hq3r · published 2026-02-17 · updated 2026-03-05
- Severity
- Critical
- CVSS score
- 9.3
- Chance of exploitation (EPSS)
- 0.55%
- Fixed in
- 2026.2.6
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Total
- CISA SSVC
In affected versions of the optional Nextcloud Talk plugin (installed separately; not bundled with the core OpenClaw install), an untrusted webhook field (actor.name, display name) could be treated as an allowlist identifier. An attacker could change their Nextcloud display name to match an allowlisted user ID and bypass DM or room allowlists.
Upgrade @openclaw/nextcloud-talk to 2026.2.6 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
6b4b6049b47c3329a7014509594647826669892d
Upgrade @openclaw/nextcloud-talk to >= 2026.2.6.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @openclaw/nextcloud-talk | npm | <= 2026.2.2 | 2026.2.6 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.