CVE-2026-32922Disclosure(openclaw / openclaw)

LOWCVSS 9.4 · CRITICAL

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Patch openclaw openclaw systems immediately
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: High priority (within 72h)

NVD description

OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with broader scopes by failing to constrain newly minted scopes to the caller's current scope set. Attackers can obtain operator.admin tokens for paired devices and achieve remote code execution on connected nodes via system.run or gain unauthorized gateway-admin access.

2.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-266

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • openclaw

Threat summary

  • Public PoC is present in monitored signal
  • Patch or workaround signal is available
  • 10 mentions across 4 observed days
  • Momentum state: stable

What's happening

  • PoC mentioned or linked in 1 signal
  • Patch or workaround mentioned in 5 signals
  • Technical details provided in 10 signals
  • Disclosure: 5 classified signals
  • Discloure: 1 classified signal
  • Peaked 3d ago at 4 mentions (2026-03-29); latest day: 1
  • 10 total mentions across 4 days

Affected systems

Vendors
Products
openclaw

Deep dive

Activity timeline10 mentions / 4d
01234Mentions · 2026-03-29: 4Mentions · 2026-03-30: 4Mentions · 2026-03-31: 1Mentions · 2026-04-19: 1PoC Mentioned / Linked · 2026-03-30: 1Patch / Workaround · 2026-03-29: 1Patch / Workaround · 2026-03-30: 2Patch / Workaround · 2026-03-31: 1Patch / Workaround · 2026-04-19: 1Technical Details · 2026-03-29: 4Technical Details · 2026-03-30: 4Technical Details · 2026-03-31: 1Technical Details · 2026-04-19: 103-2903-3003-3104-19
Signal classification4 categories
Disclosure
550.0%
Patch
330.0%
Discloure
110.0%
General
110.0%
Referenced assets5 URLs
Classification over time
DateTotalLabels
2026-03-294
Disclosure3Patch1
2026-03-304
Disclosure1Discloure1General1Patch1
2026-03-311
Patch1
2026-04-191
Disclosure1
Full discourse10 posts
  • Null Hype@nullhypeai
    Disclosure

    The growth curve here maps almost perfectly to OpenClaw's security implosion timeline. OpenClaw hit 346K stars but then came CVE-2026-25253 (CVSS 8.8), CVE-2026-32922 (CVSS 9.9), 800+ malicious skills in ClawHub covering 20% of the registry, and Microsoft telling enterprises to avoid it entirely. Hermes went from under 5,000 stars in March to 100K by mid-April, and the inflection point aligns with the week Meta and Microsoft issued their internal bans. The $6-8/month self-hosted stack with zero telemetry isn't just a feature, it's the exact opposite of everything that went wrong with OpenClaw's architecture. Developers aren't just adopting Hermes. They're fleeing to it.

    Post summary

    The post announces two high‑severity CVEs in OpenClaw, noting Microsoft’s recommendation for enterprises to avoid the product, and contextualizes the impact on community adoption.

    0003071
    252 followersView on X
  • PurpleOps@PurpleOps_io
    Patch

    🚨 Critical CVEs Today: OpenClaw Platform (CVSS 9.8-9.9) Affected: OpenClaw Platform OpenClaw components expose multiple high-severity flaws spanning privilege escalation, authorization bypass, and pairing verification risks. - CVE-2026-32922 (CVSS 9.9) OpenClaw before 2026.3.11 contains a privilege escalation in device.token.rotate that can let callers with operator.pairing scope mint tokens with broader scopes; attackers can obtain operator.admin tokens for paired devices and achieve remote code execution on connected nodes via http://system.run or gain unauthorized gateway-admin access. Affected versions: before 2026.3.11. - CVE-2026-32924 (CVSS 9.8) OpenClaw before 2026.3.12 contains an authorization bypass vulnerability where Feishu reaction events with omitted chat_type are misclassified as p2p conversations instead of group chats, enabling bypass of groupAllowFrom and requireMention protections in group chat reaction-derived events. Affected versions: before 2026.3.12. - CVE-2026-32973 (CVSS 9.8) OpenClaw before 2026.3.11 contains an exec allowlist bypass vulnerability where matchesExecAllowlistPattern improperly normalizes patterns with lowercasing and glob matching that overmatches on POSIX paths; attackers can exploit the ? wildcard matching across path segments to execute commands or paths not intended by operators. Affected versions: before 2026.3.11. - CVE-2026-32975 (CVSS 9.8) OpenClaw before 2026.3.12 contains a weak authorization vulnerability in Zalouser allowlist mode that matches mutable group display names instead of stable group identifiers; attackers can create groups with identical names to allowlisted groups to bypass channel authorization and route messages from unintended groups to the agent. Affected versions: before 2026.3.12. - CVE-2026-32987 (CVSS 9.8) OpenClaw before 2026.3.13 allows bootstrap setup codes to be replayed during device pairing verification in src/infra/device-bootstrap.ts; attackers can verify a valid bootstrap code multiple times before approval to escalate pending pairing scopes, including privilege escalation to operator.admin. Affected versions: before 2026.3.13. 🛠️ Action • Patch/upgrade to fixed OpenClaw versions 2026.3.11+ for CVE-2026-32922 and CVE-2026-32973, 2026.3.12+ for CVE-2026-32924 and CVE-2026-32975, and 2026.3.13+ for CVE-2026-32987. • Prioritize internet-facing instances and edge appliances first. • If no fix yet appears for any CVE, apply vendor-murnished mitigations and reduce exposure (disable feature/module, restrict access). • Add detections for exploitation patterns (token-rotation misuse, reaction-event anomalies, unusual path-matching behaviors, and replay attempts in pairing flows). • Hunt for indicators around the affected services during disclosure-to-now window (logs, EDR, WAF). • Validate remediation (version checks, config verification) and monitor for reversion

    Post summary

    The tweet announces multiple high‑severity CVEs affecting OpenClaw Platform, details the nature of each flaw, and provides specific patch versions and mitigation steps.

    0001082
    96 followersView on X
  • botnewsnetwork@botnewsnetwork
    Discloure

    [BNN SECURITY] 🔒 CVSS 9.9 THE NIGHT BEFORE CLAWCON TOKYO Four new OpenClaw CVEs disclosed today — on top of this morning's sandbox escape batch. Seven total on a single Sunday. March: 70+. • CVE-2026-32922 (9.9 CRITICAL): Rotate a token, get admin. From there: RCE on connected nodes or full gateway takeover. Affects all versions before 2026.3.11. • CVE-2026-32975 (9.8 CRITICAL): No-auth channel bypass via group name matching. Attackers create a group with the same name as an allowlisted one. No credentials needed. • CVE-2026-32972 (HIGH): Operator→admin privilege escalation via browser profile management routes. • CVE-2026-32978 (HIGH): You approve command A. Command B runs. TOCTOU-class bypass in the human-in-the-loop approval mechanism — the same mechanism plugin approval hooks (shipped yesterday in v2026.3.28) were built to strengthen. THE ONE THAT MATTERS CVE-32978 is the story within the story. The approval flow that operators rely on as a last line of defense has a swap window between display and execution. You see "list files." You click approve. "Delete database" runs. It's a time-of-check-to-time-of-use race condition in the trust boundary between human and agent. This is the same class of vulnerability that makes autonomous agent execution dangerous — and it was sitting in the manual approval path that's supposed to be the safety net. PATCH STATUS All four patched in v2026.3.11+. Current release: v2026.3.28. If you updated, you're covered. If you haven't updated and you're running a self-hosted gateway with node connections: patch tonight. Not tomorrow. Tonight. ClawCon Tokyo opens in hours. The timing is notable but not the point. The point is that the approval mechanism — the thing you trust when you don't trust the agent — had a hole in it. 📎 Via @thehackerwire @redpacketsecurity #BNN #OpenClaw #CVE #Security #ClawConTokyo

    Post summary

    The post announces four new critical OpenClaw CVEs, detailing their severity, impact, and patch status, without indicating active exploitation or providing a PoC.

    00010138
    29 followersView on X
  • Orizon@OrizonCyber
    Patch

    🚨 CVE-2026-32922 — CVSS 9.9/10 ██████████ OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with... Severity: CRITICAL Patch now. #cybersecurity #CVE https://t.co/YOXQ4U0QmG

    Post summary

    The tweet announces CVE‑2026‑32922, a critical privilege‑escalation flaw in OpenClaw before version 2026.3.11, and urges users to apply the available patch immediately.

    1000029
    11 followersView on X
  • CarloX@carloxthebot
    Patch

    OpenClaw CVE-2026-32922: CVSS 9.9. Low-priv pairing token → full admin RCE + key theft. 135,000 instances still exposed. Plus sandbox bypass CVE-2026-32915 (8.8). Fix: upgrade to 2026.3.11+, bind to localhost. Run: openclaw update #OpenClaw #Security

    Post summary

    The tweet announces severe OpenClaw vulnerabilities, provides detailed technical information, and immediately offers a patch recommendation.

    0000054
    24 followersView on X
  • 0day Signal@0dayPublishing
    Disclosure

    🚨 CVE-2026-32922: OpenClaw < 2026.3.11 - Privilege... Scope validation bypass in token rotation lets operator.pairing escalate to operator.admin, then RCE via http://system.run - c... https://zerodaysignal.com/vulnerability/CVE-2026-32922 #netsec #vulnerability #CVE #sysadmin #zeroday

    Post summary

    The post announces a privilege escalation vulnerability in OpenClaw 2026.3.11 that allows token rotation bypass, elevation to admin, and remote code execution via system.run, with details referenced through a zerodaysignal link.

    0000075
    194 followersView on X
  • CVE Tracker@CVE__Tracker
    General

    The weekend cut of the critical list begins with Top exposure is CVE-2026-32922 at CVSS 9.4. #CyberSecurity #ThreatIntel #CVE #CriticalVulnerability #VulnerabilityManagement https://t.co/izXihhe9bU

    Post summary

    The tweet lists CVE-2026-32922 as a top exposure with a CVSS of 9.4 but offers no further details or actionable information.

    0000062
  • The Hacker Wire@TheHackerWire
    Disclosure

    🔴 CVE-2026-32922 - Critical OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with broader scopes by failin... https://www.thehackerwire.com/vulnerability/CVE-2026-32922/ https://t.co/E2ZqNGb6pj

    Post summary

    The tweet announces CVE‑2026‑32922, a privilege escalation flaw in OpenClaw before 2026.3.11 that lets users with operator.pairing scope mint higher‑scoped tokens.

    0000050
    163 followersView on X
  • CVEFind.com@CveFindCom
    Disclosure

    [CVE-2026-32922: CRITICAL] Vulnerability in OpenClaw allows privilege escalation through device.token.rotate. Attackers can gain admin tokens and execute code or access gateway-admin without authorization.#cve,CVE-2026-32922,#cybersecurity https://cvefind.com/CVE-2026-32922

    Post summary

    The tweet announces CVE-2026-32922, a critical privilege‑escalation flaw in OpenClaw that lets attackers obtain admin tokens and execute code on the gateway; no PoC, exploit, patch, or active exploitation details are provided.

    0000063
    617 followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-32922 OpenClaw before 2026.3.11 contains a privilege escalation vulnerability in device.token.rotate that allows callers with operator.pairing scope to mint tokens with bro… https://www.cve.org/CVERecord?id=CVE-2026-32922

    Post summary

    The note details a privilege‑escalation vulnerability in OpenClaw’s device.token.rotate endpoint (pre‑2026.3.11), but provides no PoC, exploit code, or evidence of active exploitation.

    0000084
    56.9K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appopenclawopenclaw-node.js-

Explore more