Skip to main content

OpenClaw CVE-2026-53843

| EUVDEUVD-2026-37145 HIGH
Insufficient Session Expiration (CWE-613)
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise previously paired device
  2. Delivery
    Replay pairing-scoped session over WebSocket
  3. Exploit
    Request new node token post-revocation
  4. Execution
    Re-establish node-level WebSocket authority
  5. Impact
    Read/modify node state

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
Exploitation Conditions

The attacker must already possess a device that has been successfully paired with the target OpenClaw node and must retain the pairing-scoped device session material; revocation of the node token must have occurred (otherwise there is nothing to bypass). Exploitation is over the network to the OpenClaw WebSocket node interface and requires no user interaction, but it is gated by the PR:L pre-existing low-privilege foothold on a paired device, so it is not exploitable by a fully external unauthenticated attacker against a default deployment that has never paired a device with the attacker. It is limited to OpenClaw versions before 2026.5.26.

Impact

The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) yields 8.7 (High), reflecting network-reachable, low-complexity exploitation by an attacker who already holds low-privilege credentials - specifically, control of a previously paired device. There is no CISA KEV listing, no EPSS score provided, and no public exploit identified at time of analysis, so this is best treated as a real but not yet mass-exploited issue. The practical risk is concentrated in scenarios where revocation is the primary control after device compromise or insider offboarding: in those scenarios the impact is severe because the defender believes access is cut when it is not. For deployments where devices are never revoked, the real-world urgency is lower than the CVSS would suggest.

Exploit ScenarioDerived

An attacker compromises or retains physical/logical control of a device that was previously paired with an OpenClaw node - for example, a contractor's laptop after offboarding or a stolen IoT controller. The operator revokes the device's node token believing access is cut, but the attacker's surviving pairing-scoped session is replayed over WebSocket to request a new node token, restoring node-level read/write authority without any new approval step. No public exploit is identified at this time, so weaponization would require reverse-engineering the pairing/token flow from the patched diff.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 16, 2026

Authorization bypass in OpenClaw before 2026.5.26 allows an attacker with a previously paired device to re-establish WebSocket node-level authority after the session has been revoked, effectively defeating the revocation control. The flaw stems from a surviving pairing-scoped device session that can mint new node tokens without renewed approval, letting authenticated attackers retain unauthorized node-level access longer than intended. No public exploit identified at time of analysis, but the issue is acknowledged in a GitHub Security Advisory (GHSA-q99w-vh6v-q3v7) and a VulnCheck advisory.

RemediationAI

Vendor-released patch: OpenClaw 2026.5.26 - upgrade to this version or later, per the GitHub Security Advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-q99w-vh6v-q3v7 and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-node-token-revocation-bypass-via-pairing-scoped-device-session. Until the upgrade is rolled out, operators should treat token revocation as insufficient on its own and additionally unpair the affected device at the pairing layer (removing the device pairing entry, not just revoking issued tokens), which forces a fresh approval flow but disrupts legitimate use of that device until re-pairing. As a network-layer compensating control, restrict WebSocket node endpoints to known management networks or mTLS-authenticated clients so that a still-trusted but suspect device cannot reach the node API path used to re-mint tokens; this adds operational overhead and may break remote management for legitimate paired devices that connect from outside the allowed network.

Affected VersionsENISA

OpenClaw 0 <2026.5.26

Affected Packages

npm openclaw fix: 2026.5.26

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OpenClaw uses a pairing-and-token model in which a device is paired with a node and then issued scoped session tokens to authenticate WebSocket connections to node-level APIs. The vulnerability is a CWE-613 Insufficient Session Expiration issue: the pairing-scoped device session is not fully invalidated when a node token is revoked, so the still-trusted device session can be reused to obtain fresh node-level tokens. In effect, revocation acts only on the derived token rather than on the underlying pairing session that authorizes token issuance, breaking the trust-hierarchy assumption that revoking a token cuts off downstream access.

Know when Openclaw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Network-reachable WebSocket endpoint (AV:N/AC:L), but attacker must already control a paired device session (PR:L), no user interaction, and node-level access yields high C/I/A within the same node (S:U).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Jun 16, 2026 - 20:02 EUVD

DescriptionCVE.org

OpenClaw before 2026.5.26 contains an authorization bypass vulnerability where a surviving pairing-scoped device session can re-establish node token authority after revocation. Attackers with a paired device can regain WebSocket node-level access without renewed approval, weakening revocation controls and maintaining unauthorized access longer than intended.

Executive ViewAI

Why It Matters

OpenClaw installations are vulnerable to an authorization bypass (CVE-2026-53843, CVSS 8.7) that defeats session revocation controls for paired devices. Administrators cannot effectively remove access for previously authorized devices through standard administrative procedures, creating persistent unauthorized access. Organizations using OpenClaw for device or infrastructure access control cannot guarantee that revoked sessions are actually terminated.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Implement network segmentation to restrict device-to-node communication; disable all non-essential device pairings to reduce attack surface; deploy monitoring and alerting on WebSocket token creation and node-level access attempts; review authentication and session logs for evidence of token reuse or access attempts after documented revocation. Establish expedited deployment process for OpenClaw 2026.5.26+ upon vendor release.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Threat Intel
1
1 sources
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-100530 HIGH POC
8.5 Sep 26

Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a

CVE-2026-32064 HIGH POC
8.5 Mar 21

Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy