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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r5h9-vjqc-hq3r can be triaged on real exposure rather than presence alone.

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 is the EPSS score for GHSA-r5h9-vjqc-hq3r?

GHSA-r5h9-vjqc-hq3r has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

GHSA-r5h9-vjqc-hq3r — @openclaw/nextcloud-talk

Fix: openclaw/openclaw@660f872

GHSA-r5h9-vjqc-hq3r is a CWE-863 vulnerability in @openclaw/nextcloud-talk. A fix is available for @openclaw/nextcloud-talk — see the affected versions and patch details below.

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

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r5h9-vjqc-hq3r.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openclaw/nextcloud-talknpm

2Kdownloads / week

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`npm install @openclaw/nextcloud-talk@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r5h9-vjqc-hq3r can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-r5h9-vjqc-hq3r across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works