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

How do I mitigate GHSA-wh94-p5m6-mr7j if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.3%, placing it in the 25th 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

Not in CISA KEV

GHSA-wh94-p5m6-mr7j — openclaw

Fix: openclaw/openclaw@7758160

GHSA-wh94-p5m6-mr7j is a CWE-862 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

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

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

Exploitation Status

No confirmed exploitation observed yet

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-wh94-p5m6-mr7j.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

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

openclawnpm

3.3Mdownloads / 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`npm install openclaw@2026.2.18`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

≤ 2026.2.17

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works