CVE-2026-53852 [Low] | Security Bypass in Openclaw

OpenClaw before 2026.4.25 contains a scope containment bypass vulnerability in device re-pairing that allows authenticated operators to restore broader scopes than intended by submitting empty-scope re-pairing requests. Attackers can exploit this by sending re-pairing requests with empty scope sets to skip containment guards and retain unauthorized device access.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-17	—	0.17%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-17

—

0.17%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.3	4.0	LOW	`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network. Attack complexity (AC:L) Exploitation conditions are straightforward and stable. Attack requirements (AT:P) Additional preconditions must be present for exploitation. Privileges required (PR:L) Low privileges are required. User interaction (UI:N) No user interaction is required. Vulnerable system confidentiality impact (VC:L) Limited confidentiality impact on the vulnerable system. Vulnerable system integrity impact (VI:L) Limited integrity impact on the vulnerable system. Vulnerable system availability impact (VA:N) No availability impact on the vulnerable system. Subsequent system confidentiality impact (SC:N) No confidentiality impact on subsequent systems. Subsequent system integrity impact (SI:N) No integrity impact on subsequent systems. Subsequent system availability impact (SA:N) No availability impact on subsequent systems. Exploit maturity (threat) (E:X) Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked). Confidentiality requirement (CR:X) Not defined: insufficient information; scoring treats this like High (worst case). Integrity requirement (IR:X) Not defined: insufficient information; scoring treats this like High (worst case). Availability requirement (AR:X) Not defined: insufficient information; scoring treats this like High (worst case). Modified attack vector (MAV:X) Not defined: scoring uses the Base Attack Vector (AV). Modified attack complexity (MAC:X) Not defined: scoring uses the Base Attack Complexity (AC). Modified attack requirements (MAT:X) Not defined: scoring uses the Base Attack Requirements (AT). Modified privileges required (MPR:X) Not defined: scoring uses the Base Privileges Required (PR). Modified user interaction (MUI:X) Not defined: scoring uses the Base User Interaction (UI). Modified vulnerable system confidentiality impact (MVC:X) Not defined: scoring uses the Base VC metric. Modified vulnerable system integrity impact (MVI:X) Not defined: scoring uses the Base VI metric. Modified vulnerable system availability impact (MVA:X) Not defined: scoring uses the Base VA metric. Modified subsequent system confidentiality impact (MSC:X) Not defined: scoring uses the Base SC metric. Modified subsequent system integrity impact (MSI:X) Not defined: scoring uses the Base SI metric. Modified subsequent system availability impact (MSA:X) Not defined: scoring uses the Base SA metric. Safety (supplemental) (S:X) Not evaluated. Automatable (supplemental) (AU:X) Not evaluated. Recovery (supplemental) (R:X) Not evaluated. Value density (supplemental) (V:X) Not evaluated. Vulnerability response effort (supplemental) (RE:X) Not evaluated. Provider urgency (supplemental) (U:X) Not evaluated.	—	—	[email protected]
5.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	2.5	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.3

4.0

LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L): Exploitation conditions are straightforward and stable.
Attack requirements (AT:P): Additional preconditions must be present for exploitation.
Privileges required (PR:L): Low privileges are required.
User interaction (UI:N): No user interaction is required.
Vulnerable system confidentiality impact (VC:L): Limited confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:L): Limited integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N): No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N): No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N): No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N): No availability impact on subsequent systems.
Exploit maturity (threat) (E:X): Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X): Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X): Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X): Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X): Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X): Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X): Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X): Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X): Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X): Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X): Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X): Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X): Not evaluated.
Automatable (supplemental) (AU:X): Not evaluated.
Recovery (supplemental) (R:X): Not evaluated.
Value density (supplemental) (V:X): Not evaluated.
Vulnerability response effort (supplemental) (RE:X): Not evaluated.
Provider urgency (supplemental) (U:X): Not evaluated.

—

[email protected]

5.4

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

2.5

[email protected]

Affected software / configurations for CVE-2026-53852

Vendor	Product	Version	Raw CPE
openclaw	openclaw	< 2026.4.25	cpe:2.3:a:openclaw:openclaw::::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta1::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta10::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta11::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta2::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta3::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta4::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta5::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta6::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta7::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta8::::node.js::*
openclaw	openclaw	2026.4.25	cpe:2.3:a:openclaw:openclaw:2026.4.25:beta9::::node.js::*

References for CVE-2026-53852

URL	Tags
https://github.com/openclaw/openclaw/security/advisories/GHSA-8mg9-j9cf-54cj	Vendor Advisory
https://www.vulncheck.com/advisories/openclaw-scope-bypass-via-empty-scope-device-re-pairing	Third Party Advisory

URL

CVE-2026-53852 | OpenClaw < 2026.4.25 - Scope Bypass via Empty-Scope Device Re-pairing

Exploit prediction scoring system (EPSS) score for CVE-2026-53852

Common vulnerability scoring system (CVSS) metrics for CVE-2026-53852

Weakness enumeration for CVE-2026-53852

GitHub Security Advisory for CVE-2026-53852

Affected software / configurations for CVE-2026-53852

References for CVE-2026-53852