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

GHSA-gg9v-mgcp-v6m7

CRITICAL

GHSA-gg9v-mgcp-v6m7 is a critical-severity (CVSS 9.8) CWE-648 vulnerability in openclaw. O3 Security confirms whether GHSA-gg9v-mgcp-v6m7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Unbound bootstrap setup codes allow privilege escalation during pairing

Also known asCVE-2026-41386
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

Bootstrap setup codes were not bound to the intended device role and scopes, allowing first-use privilege escalation during pairing.

Current Maintainer Triage

  • Status: open
  • Normalized severity: high
  • Assessment: Real first-use bootstrap privilege-escalation bug fixed and shipped in v2026.3.22+, so keep open for publication with current severity.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published npm version: 2026.3.31
  • Vulnerable version range: <=2026.3.13-1
  • Patched versions: >= 2026.3.22
  • First stable tag containing the fix: v2026.3.22

Fix Commit(s)

  • a600c72ed7d0045a27f58bf031d2b36ecb0141c9 — 2026-03-22T23:57:15-07:00

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.3.22

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

Frequently Asked Questions

## Summary Bootstrap setup codes were not bound to the intended device role and scopes, allowing first-use privilege escalation during pairing. ## Current Maintainer Triage - Status: open - Normalized severity: high - Assessment: Real first-use bootstrap privilege-escalation bug fixed and shipped in v2026.3.22+, so keep open for publication with current severity. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.13-1` - Patched versions: `>= 2026.3.22` - First stable tag containing the fix: `v2026.3.2
O3 Security · Impact-Aware SCA

Is GHSA-gg9v-mgcp-v6m7 in your dependencies?

O3 detects GHSA-gg9v-mgcp-v6m7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.