Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-r5h9-vjqc-hq3r
No affected components available
Summary
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.
Details
Nextcloud Talk webhook payloads provide a stable sender identifier (actor.id) and a mutable display name (actor.name). In affected versions, the plugin’s allowlist matching accepted equality on the display name, which is attacker-controlled.
Affected Packages / Versions
- Package:
@openclaw/nextcloud-talk(npm) - Affected:
<= 2026.2.2 - Fixed:
>= 2026.2.6
Note: This advisory applies to the optional Nextcloud Talk plugin package. Core openclaw is not impacted unless you installed and use @openclaw/nextcloud-talk.
Fix Commit(s)
Timeline
- Introduced: 660f87278c9f292061e097441e0b10c20d62b31b (2026-01-20)
- Fixed in repo: 6b4b6049b47c3329a7014509594647826669892d (2026-02-04 UTC)
- First fixed tag containing the change: v2026.2.3
- First fixed npm release of
@openclaw/nextcloud-talk:2026.2.6(published 2026-02-07 UTC)
Mitigation
Upgrade @openclaw/nextcloud-talk to >= 2026.2.6.
Release Process Note
The patched version range is set to the first npm release that contains the fix. Once you are ready, you can publish this advisory without additional version edits.
Thanks @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard