CVE-2026-25253
Openclaw ≤ 2026.1.29
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-25253 is a high-severity Incorrect Resource Transfer Between Spheres (CWE-669) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Escape to Host (T1611); ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25253 is a vulnerability in OpenClaw (also known as clawdbot or Moltbot) versions prior to 2026.1.29. The issue stems from the software obtaining a gatewayUrl value from a query string and automatically establishing a WebSocket connection without user prompting, which results in sending a token value over that connection. This flaw is rated with a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is associated with CWE-669.
Attackers can exploit this vulnerability remotely without privileges by tricking a user into interacting with a malicious link containing a controlled gatewayUrl in the query string. Upon user interaction, such as clicking the link, the software connects to the attacker's WebSocket endpoint and transmits the token, enabling high-impact confidentiality, integrity, and availability consequences.
Mitigation guidance from advisories, including the GitHub Security Advisory GHSA-g8p2-7wf7-98mq, recommends updating to OpenClaw version 2026.1.29 or later. Further details on patches and exploitation techniques are provided in references such as depthfirst.com, ethiack.com, openclaw.ai/blog, and an X post by @0xacb.
References highlight real-world exploitation demonstrations, including one-click remote code execution to steal Moltbot data and keys, as detailed in the linked blog posts.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5280
Vulnerability Data
OpenClaw (aka clawdbot or Moltbot) before 2026.1.29 obtains a gatewayUrl value from a query string and automatically makes a WebSocket connection without prompting, sending a token value.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved information flow authorizations between system components and connected systems, directly stopping improper resource transfers across spheres.
Prevents unintended information leakage through shared system resources when crossing sphere boundaries.
Monitors and controls communications at external and key internal boundaries to block unauthorized transfers between trust domains.
Enforces logical access authorizations that limit resource transfers to only approved sphere crossings.
Separates user functionality from system management functions to avoid improper resource or behavior transfer between privilege spheres.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Least-privilege authorization policies directly constrain resource transfers across security domains.
Protecting data-in-transit can limit exposure during inter-sphere transfers but does not address control-flow or authorization errors.
Logical segmentation and access controls reduce unintended cross-sphere resource movement.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Environment separation limits unintended resource leakage between spheres.
Information-transfer rules can prevent improper resource hand-off between spheres.
Access-control policies limit unintended control over transferred resources.
Managing access rights reduces risk of unauthorized resource transfer.
Network-security controls can block improper cross-sphere transfers.
Network segregation directly limits unintended resource movement between spheres.