CVE-2026-44111
Openclaw ≤ 2026.4.15
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/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-44111 is a low-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Openclaw Openclaw. Its CVSS base score is 2.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 14th 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-28188
Vulnerability Data
OpenClaw before 2026.4.15 contains an arbitrary file read vulnerability in the QMD backend memory_get function that allows callers to read any Markdown files within the workspace root. Attackers with access to the memory tool can bypass path restrictions by providing…
more
arbitrary workspace Markdown paths to read files outside canonical memory locations or indexed QMD result sets.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Arbitrary file read via path bypass directly enables reading local Markdown files from the workspace.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly validates caller-supplied Markdown paths in memory_get to reject those outside canonical locations or indexed QMD sets.
Enforces path-based access policy on the QMD backend so arbitrary workspace-root reads are denied before any file content is returned.
Restricts the memory tool's privileges to only the minimal set of Markdown files required, limiting the impact of any path bypass.
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 SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.
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 overly broad allow-lists, but does not inherently prevent their creation.
Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.
Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.
Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.
Configuration management can enforce validated input rules, yet does not directly address the design flaw of permissive lists.