Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-2pr2-hcv6-7gwv

HIGHFix: openclaw/openclaw@7a801cc

GHSA-2pr2-hcv6-7gwv is a high-severity (CVSS 7.5) CWE-613 vulnerability in openclaw. O3 Security confirms whether GHSA-2pr2-hcv6-7gwv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw's device removal and token revocation do not terminate active WebSocket sessions

Also known asCVE-2026-34503
Published
Mar 31, 2026
Updated
Apr 6, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm
3.1Mdownloads / week

Description

Summary

Removing a device or revoking its token updated stored credentials but did not disconnect already-authenticated WebSocket sessions.

Impact

A revoked device could continue using its existing live session until reconnect, extending access beyond credential removal.

Affected Component

src/gateway/server-methods/devices.ts, src/gateway/server.impl.ts

Fixed Versions

  • Affected: <= 2026.3.24
  • Patched: >= 2026.3.28
  • Latest stable 2026.3.28 contains the fix.

Fix

Fixed by commit 7a801cc451 (Gateway: disconnect revoked device sessions).

OpenClaw thanks @AntAISecurityLab for reporting.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.3.28

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pr2-hcv6-7gwv is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-2pr2-hcv6-7gwv 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-2pr2-hcv6-7gwv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Removing a device or revoking its token updated stored credentials but did not disconnect already-authenticated WebSocket sessions. ## Impact A revoked device could continue using its existing live session until reconnect, extending access beyond credential removal. ## Affected Component `src/gateway/server-methods/devices.ts, src/gateway/server.impl.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `7a801cc451` (`Gateway: disconnect revoked device sessions`). OpenClaw thanks @Ant
O3 Security · Impact-Aware SCA

Is GHSA-2pr2-hcv6-7gwv in your dependencies?

O3 detects GHSA-2pr2-hcv6-7gwv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.