CVE-2026-41377
Openclaw ≤ 2026.3.31
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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:XSummary
CVE-2026-41377 is a medium-severity Failing Open (CWE-636) vulnerability in Openclaw Openclaw. Its CVSS base score is 5.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Software Extensions (T1176); 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 SC-24 (Fail in Known State) and CM-11 (User-installed Software) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26086
Vulnerability Data
OpenClaw before 2026.3.31 contains a fail-open vulnerability in the plugin installation flow where security scan failures do not block installation. Attackers can exploit scan failures to install untrusted plugins when operators proceed despite visible scan warnings.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Fail-open plugin scan directly allows installation of untrusted extensions that can be abused for persistence/execution.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires the system to fail to a known safe state, preventing the fail-open behavior that allows untrusted plugins after scan failures.
Mandates integrity verification of software before execution, which would block installation of plugins that fail security scans.
Restricts and monitors user-installed software such as plugins, enforcing policy-based blocking rather than allowing overrides of scan warnings.
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 explicitly include designing error and failure handling to remain in a secure state.
Least-privilege policy and enforcement directly counters the permissive-access fallback example in the CWE.
Hardened baselines and configuration management reduce the chance that error paths default to insecure settings.
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.
The control forces an explicit evaluation step before any response, reducing the chance that a failure condition will default to an unsafe open state.