CVE-2026-32008
Openclaw ≤ 2026.2.21
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:XSummary
CVE-2026-32008 is a high-severity Externally Controlled Reference to a Resource in Another Sphere (CWE-610) vulnerability in Openclaw Openclaw. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 33th percentile by exploit likelihood (below the median); 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-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13267
Vulnerability Data
OpenClaw versions prior to 2026.2.21 contain an improper URL scheme validation vulnerability in the assertBrowserNavigationAllowed() function that allows authenticated users with browser-tool access to navigate to file:// URLs. Attackers can exploit this by accessing local files readable by the OpenClaw…
more
process user through browser snapshot and extraction actions to exfiltrate sensitive data.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Improper file:// URL validation directly enables local file access and extraction by the browser tool, mapping to Data from Local System.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces the navigation policy inside assertBrowserNavigationAllowed() so that file:// URLs are rejected before any local-file access occurs.
Requires validation of URL scheme and origin on every browser navigation input, blocking the externally-controlled file:// reference that leads to data exfiltration.
Enforces information-flow rules that prevent the browser-tool from moving data from the file system into the snapshot/extraction channel used by the attacker.
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.
Secure development practices directly require input validation and reference sanitization that prevent externally-controlled resource references.
Runtime monitoring of software and data flows can detect anomalous external resource accesses that result from this weakness.
Network segmentation and access controls limit the blast radius when an external reference escapes its intended sphere.
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.
Security testing can detect instances of the weakness but does not prevent it at design or coding time.
Secure development lifecycle mandates validation of all external references to prevent uncontrolled resource access.
Application security requirements explicitly call for controls against externally supplied resource identifiers.
Secure architecture principles reduce the attack surface for externally controlled references but do not prescribe specific validation rules.
Secure coding standards require input validation and canonicalization to block externally controlled resource references.
Information access restriction limits what resources can be reached, indirectly reducing impact of external references.