Summary
Nextcloud Talk allowlist bypass via actor.name display name spoofing
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-28474? CVE-2026-28474 is a critical-severity security vulnerability in @openclaw/nextcloud-talk (npm), affecting versions <= 2026.2.2. It is fixed in 2026.2.6.
- Which versions of @openclaw/nextcloud-talk are affected by CVE-2026-28474? @openclaw/nextcloud-talk (npm) versions <= 2026.2.2 is affected.
- Is there a fix for CVE-2026-28474? Yes. CVE-2026-28474 is fixed in 2026.2.6. Upgrade to this version or later.
- Is CVE-2026-28474 exploitable, and should I be worried? Whether CVE-2026-28474 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28474 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28474? Upgrade
@openclaw/nextcloud-talkto 2026.2.6 or later.