How severe is GHSA-4cqv-h74h-93j4?

GHSA-4cqv-h74h-93j4 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4cqv-h74h-93j4?

GHSA-4cqv-h74h-93j4 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-4cqv-h74h-93j4?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cqv-h74h-93j4 is resolved across your whole dependency graph.

How do I detect GHSA-4cqv-h74h-93j4 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-4cqv-h74h-93j4 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-4cqv-h74h-93j4?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4cqv-h74h-93j4 can be triaged on real exposure rather than presence alone.

Is GHSA-4cqv-h74h-93j4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4cqv-h74h-93j4 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.

When was GHSA-4cqv-h74h-93j4 published, and has it been updated?

GHSA-4cqv-h74h-93j4 was published on March 3, 2026 and was last updated on March 4, 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

MEDIUM severity

GHSA-4cqv-h74h-93j4 — openclaw

MEDIUMFix: openclaw/openclaw@747bb58

GHSA-4cqv-h74h-93j4 is a medium-severity (CVSS 6.5) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw has a Discord `allowFrom` slug-collision authorization bypass

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, 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.5Mdownloads / week

Description

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.21-2
Patched versions: >= 2026.2.22

What Changed

openclaw security audit now warns on Discord name/tag allowlist entries (DM allowlists, guild/channel users, and pairing-store entries).
Runtime authorization now prefers resolved user IDs when a configured name/tag can be resolved, without rewriting config files on disk.
Name-based entries remain supported for compatibility.

Recommendations

Prefer stable Discord user IDs for security-sensitive allowlists.
Run openclaw security audit and address warnings where practical.

Fix Commit(s)

f97c45c5b5e0698b6667bb5f6badc0cac7dabd12
747bb581b3f2264495e1fec5a0727d9f2ca1b6f1

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

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

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.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cqv-h74h-93j4 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-4cqv-h74h-93j4 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4cqv-h74h-93j4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

OpenClaw supports Discord allowlists using either user IDs or names/tags. Name/tag matching depends on slug normalization, so different user tags can collide to the same slug and unintentionally satisfy a name-based allowlist entry. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.21-2` - Patched versions: >= 2026.2.22 ## What Changed - `openclaw security audit` now warns on Discord name/tag allowlist entries (DM allowlists, guild/channel `users`, and pairing-store entries). - Runtime authorization now prefers resolved user IDs when a configured nam

O3 Security · Impact-Aware SCA

Is GHSA-4cqv-h74h-93j4 in your dependencies?

O3 Security finds GHSA-4cqv-h74h-93j4 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