How severe is GHSA-x2m8-53h4-6hch?

No CVSS score has been assigned to GHSA-x2m8-53h4-6hch yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x2m8-53h4-6hch?

GHSA-x2m8-53h4-6hch affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-x2m8-53h4-6hch?

Update openclaw to 2026.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2m8-53h4-6hch is resolved across your whole dependency graph.

How do I detect GHSA-x2m8-53h4-6hch 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-x2m8-53h4-6hch 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-x2m8-53h4-6hch actively exploited in the wild?

No public exploit code has been indexed for GHSA-x2m8-53h4-6hch 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-x2m8-53h4-6hch?

GHSA-x2m8-53h4-6hch has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th 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-x2m8-53h4-6hch?

GHSA-x2m8-53h4-6hch 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-x2m8-53h4-6hch published, and has it been updated?

GHSA-x2m8-53h4-6hch was published on April 3, 2026 and was last updated on May 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

OpenClaw: Discord voice ingress authorization can be bypassed via channel, name, and stale-role validation gapsGHSA-x2m8-53h4-6hch

Fix: openclaw/openclaw@dba96e7

GHSA-x2m8-53h4-6hch is a CWE-862 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-41382

Published

Apr 3, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-x2m8-53h4-6hch.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% 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

2.9Mdownloads / week

Description

Summary

Discord voice ingress authorization can be bypassed via channel, name, and stale-role validation gaps

Current Maintainer Triage

Status: narrow
Assessment: Real in shipped v2026.3.28 Discord voice ingress, but impact is channel/member allowlist bypass rather than a broader critical auth break and mainline fix is unreleased.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.28
Patched versions: >= 2026.3.31
First stable tag containing the fix: v2026.3.31

Fix Commit(s)

dba96e7507e0900f120e5e28e57755d69bf78759 — 2026-03-31T21:29:13+09:00

OpenClaw thanks @cyjhhh for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.31`npm install openclaw@2026.3.31`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.3.31

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.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2m8-53h4-6hch 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

## Summary Discord voice ingress authorization can be bypassed via channel, name, and stale-role validation gaps ## Current Maintainer Triage - Status: narrow - Assessment: Real in shipped v2026.3.28 Discord voice ingress, but impact is channel/member allowlist bypass rather than a broader critical auth break and mainline fix is unreleased. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.28` - Patched versions: `>= 2026.3.31` - First stable tag containing the fix: `v2026.3.31` ## Fix Commit(s) - `d

O3 Security · Impact-Aware SCA

Is GHSA-x2m8-53h4-6hch in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works