OpenClaw up to 2026.4.19 Paired-device Pairing Management authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in OpenClaw up to 2026.4.19. The affected element is an unknown function of the component Paired-device Pairing Management. The manipulation results in authorization. This vulnerability was named CVE-2026-41909. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in OpenClaw up to 2026.4.19. It has been classified as critical. Affected is an unknown functionality of the component Paired-device Pairing Management. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
OpenClaw before 2026.4.20 contains an improper authorization vulnerability in paired-device pairing management that allows limited-scope sessions to enumerate and act on pairing requests. Attackers with paired-device access can approve or operate on unrelated pending device requests within the same gateway scope.
The weakness was presented by Chia Min Jun Lennon and Hinotobi as GHSA-xrq9-jm7v-g9h7. The advisory is available at github.com. This vulnerability is traded as CVE-2026-41909 since 04/22/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The technical details are unknown and an exploit is not available.
Upgrading to version 2026.4.20 eliminates this vulnerability. Applying the patch 5a12f30441d5b0b151f550daa2c5c9e8db61e2e6 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 2026.4.0
- 2026.4.1
- 2026.4.2
- 2026.4.3
- 2026.4.4
- 2026.4.5
- 2026.4.6
- 2026.4.7
- 2026.4.8
- 2026.4.9
- 2026.4.10
- 2026.4.11
- 2026.4.12
- 2026.4.13
- 2026.4.14
- 2026.4.15
- 2026.4.16
- 2026.4.17
- 2026.4.18
- 2026.4.19
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.4.20
Patch: 5a12f30441d5b0b151f550daa2c5c9e8db61e2e6
Timeline
04/22/2026 CVE reserved04/23/2026 Advisory disclosed
04/23/2026 VulDB entry created
04/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-xrq9-jm7v-g9h7
Researcher: Chia Min Jun Lennon, Hinotobi
Status: Confirmed
CVE: CVE-2026-41909 (🔒)
GCVE (CVE): GCVE-0-2026-41909
GCVE (VulDB): GCVE-100-359178
Entry
Created: 04/23/2026 23:03Changes: 04/23/2026 23:03 (79)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.