How severe is GHSA-6p8r-6m93-557f?

GHSA-6p8r-6m93-557f has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6p8r-6m93-557f?

GHSA-6p8r-6m93-557f affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6p8r-6m93-557f?

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

How do I detect GHSA-6p8r-6m93-557f 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-6p8r-6m93-557f 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-6p8r-6m93-557f?

O3 pinpoints whether GHSA-6p8r-6m93-557f 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-6p8r-6m93-557f actively exploited in the wild?

No public exploit code has been indexed for GHSA-6p8r-6m93-557f 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 type of vulnerability is GHSA-6p8r-6m93-557f?

GHSA-6p8r-6m93-557f is classified as CWE-799 (CWE-799). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6p8r-6m93-557f published, and has it been updated?

GHSA-6p8r-6m93-557f was published on April 3, 2026 and was last updated on May 6, 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-6p8r-6m93-557f

LOW

GHSA-6p8r-6m93-557f is a low-severity (CVSS 3.7) CWE-799 vulnerability in openclaw. O3 Security confirms whether GHSA-6p8r-6m93-557f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Fake DeviceToken Bypasses Shared Auth Rate Limiting

Also known asCVE-2026-41333

Published

Apr 3, 2026

Updated

May 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

openclawnpm

3.2Mdownloads / week

Description

Summary

Fake DeviceToken Bypasses Shared Auth Rate Limiting

Current Maintainer Triage

Status: narrow
Normalized severity: low
Assessment: Real in shipped mixed WS auth flow, but practical risk is mostly weak shared-password deployments since strong shared tokens remain non-bruteforceable.

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)

af0c0862f22ca4492406a3103d05e3628f94cbe9 — 2026-03-31T09:08:57+09:00

Release Process Note

The fix is already present in released version 2026.3.31.

OpenClaw thanks @kexinoh of Tencent zhuque Lab (https://github.com/Tencent/AI-Infra-Guard) for reporting.

Affected Packages

1 total 1 fixed

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

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.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6p8r-6m93-557f 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-6p8r-6m93-557f 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-6p8r-6m93-557f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Fake DeviceToken Bypasses Shared Auth Rate Limiting ## Current Maintainer Triage - Status: narrow - Normalized severity: low - Assessment: Real in shipped mixed WS auth flow, but practical risk is mostly weak shared-password deployments since strong shared tokens remain non-bruteforceable. ## 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) - `af0c0862f22ca4492406a3103d05e3628f94cbe9`

O3 Security · Impact-Aware SCA

Is GHSA-6p8r-6m93-557f in your dependencies?

O3 detects GHSA-6p8r-6m93-557f 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