How severe is GHSA-r5h9-vjqc-hq3r?

No CVSS score has been assigned to GHSA-r5h9-vjqc-hq3r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r5h9-vjqc-hq3r?

GHSA-r5h9-vjqc-hq3r affects the following packages: @openclaw/nextcloud-talk (npm). Ecosystems affected: npm.

How do I fix GHSA-r5h9-vjqc-hq3r?

Update @openclaw/nextcloud-talk to 2026.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5h9-vjqc-hq3r is resolved across your whole dependency graph.

How do I detect GHSA-r5h9-vjqc-hq3r in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/nextcloud-talk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r5h9-vjqc-hq3r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-r5h9-vjqc-hq3r?

O3 pinpoints whether GHSA-r5h9-vjqc-hq3r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r5h9-vjqc-hq3r actively exploited in the wild?

No public exploit code has been indexed for GHSA-r5h9-vjqc-hq3r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-r5h9-vjqc-hq3r?

GHSA-r5h9-vjqc-hq3r is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r5h9-vjqc-hq3r published, and has it been updated?

GHSA-r5h9-vjqc-hq3r was published on February 17, 2026 and was last updated on March 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-r5h9-vjqc-hq3r

GHSA-r5h9-vjqc-hq3r is a CWE-863 vulnerability in @openclaw/nextcloud-talk. O3 Security confirms whether GHSA-r5h9-vjqc-hq3r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Nextcloud Talk allowlist bypass via actor.name display name spoofing

Also known asCVE-2026-28474

Published

Feb 17, 2026

Updated

Mar 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦@openclaw/nextcloud-talk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openclaw/nextcloud-talk`	all versions	2026.2.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/nextcloud-talk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @openclaw/nextcloud-talk to 2026.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5h9-vjqc-hq3r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-r5h9-vjqc-hq3r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r5h9-vjqc-hq3r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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 at

O3 Security · Impact-Aware SCA

Is GHSA-r5h9-vjqc-hq3r in your dependencies?

O3 detects GHSA-r5h9-vjqc-hq3r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works