How severe is GHSA-wh94-p5m6-mr7j?

No CVSS score has been assigned to GHSA-wh94-p5m6-mr7j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wh94-p5m6-mr7j?

GHSA-wh94-p5m6-mr7j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-wh94-p5m6-mr7j?

Update openclaw to 2026.2.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wh94-p5m6-mr7j is resolved across your whole dependency graph.

How do I detect GHSA-wh94-p5m6-mr7j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. 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-wh94-p5m6-mr7j 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-wh94-p5m6-mr7j?

O3 pinpoints whether GHSA-wh94-p5m6-mr7j 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-wh94-p5m6-mr7j actively exploited in the wild?

No public exploit code has been indexed for GHSA-wh94-p5m6-mr7j 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-wh94-p5m6-mr7j?

GHSA-wh94-p5m6-mr7j has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-wh94-p5m6-mr7j?

GHSA-wh94-p5m6-mr7j is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wh94-p5m6-mr7j published, and has it been updated?

GHSA-wh94-p5m6-mr7j was published on February 20, 2026 and was last updated on February 23, 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-wh94-p5m6-mr7j

OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows

Also known asCVE-2026-27484

Published

Feb 20, 2026

Updated

Feb 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk9th percentile+0.16%

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.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.4Mdownloads / week

Description

Overview

Discord moderation action handling (timeout, kick, ban) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context.

Impact

In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields.

Affected Packages / Versions

Package: openclaw (npm)
Latest published affected version (as of 2026-02-19): 2026.2.17
Affected range: <=2026.2.17
Fixed in planned next release: 2026.2.18

Fix

Moderation authorization now uses trusted sender context (requesterSenderId) instead of untrusted action params.
Added permission checks for required guild capabilities per action.

Fix Commit(s)

775816035ecc6bb243843f8000c9a58ff609e32d

Thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.18

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. 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 to 2026.2.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wh94-p5m6-mr7j 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-wh94-p5m6-mr7j 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-wh94-p5m6-mr7j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Overview Discord moderation action handling (`timeout`, `kick`, `ban`) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context. ## Impact In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published affected version (as of 2026-02-19): `2026.2.17` - Affected range: `<=2026.2.17` - Fixed in planned next release: `2026.2.18` ## Fi

O3 Security · Impact-Aware SCA

Is GHSA-wh94-p5m6-mr7j in your dependencies?

O3 detects GHSA-wh94-p5m6-mr7j 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