Loading...
Skip to main content

CVE-2026-28474 — Vulnerability in @openclaw/nextcloud-talk — CVE...

CRITICAL

Nextcloud Talk allowlist bypass via actor.name display name spoofing

Published February 17, 2026Updated March 5, 2026Source: osv

Summary

## 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) - [6b4b6049b47c3329a7014509594647826669892d](https://github.com/openclaw/openclaw/commit/6b4b6049b47c3329a7014509594647826669892d) ## Timeline - Introduced: [660f87278c9f292061e097441e0b10c20d62b31b](https://github.com/openclaw/openclaw/commit/660f87278c9f292061e097441e0b10c20d62b31b) (2026-01-20) - Fixed in repo: [6b4b6049b47c3329a7014509594647826669892d](https://github.com/openclaw/openclaw/commit/6b4b6049b47c3329a7014509594647826669892d) (2026-02-04 UTC) - First fixed tag containing the change: [v2026.2.3](https://github.com/openclaw/openclaw/releases/tag/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](https://aisle.com/) for reporting.

Advisory Timeline

  • First published February 17, 2026 (237 days ago).
  • Last revised March 5, 2026 — 16 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

npm
Update @openclaw/nextcloud-talk to 2026.2.6 or later
npm install @openclaw/nextcloud-talk@2026.2.6

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: npm (1).

PackageEcosystemAffectedFixed In
@openclaw/nextcloud-talk
npm
All versions2026.2.6

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Frequently Asked Questions

What is CVE-2026-28474?
Nextcloud Talk allowlist bypass via actor.name display name spoofing This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
How do I check if my project is affected by CVE-2026-28474?
CVE-2026-28474 affects @openclaw/nextcloud-talk. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-28474 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.1

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-r5h9-vjqc-hq3r

Related CVEs

  • CVE-2026-107722
    CRITICAL

    fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion

  • CVE-2026-108261
    CRITICAL

    TinaCMS admin preview iframe loads an attacker-controlled origin from the URL fragment

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies