CVE-2026-41388
Openclaw ≤ 2026.3.31
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/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-41388 is a medium-severity Incomplete Internal State Distinction (CWE-372) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Server Software Component (T1505); ranked at the 23th 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 CM-6 (Configuration Settings) and CM-3 (Configuration Change Control) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26097
Vulnerability Data
OpenClaw before 2026.3.31 contains a configuration management vulnerability where startup migration treats empty-array settings as missing values. Attackers can restart the application to rehydrate revoked Tlon configuration from file state, bypassing intended revocation controls.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability bypasses config revocation on restart, directly enabling persistence via server software component rehydration from file state.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces correct application and validation of configuration settings so that revoked values cannot be silently rehydrated from file state on restart.
Requires controlled, auditable changes to configuration, preventing unauthorized or incomplete revocation state from persisting across application restarts.
Protects configuration data integrity and can detect unauthorized or inconsistent state restoration that bypasses intended revocation.
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.
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 state-machine flaws that manifest as incomplete internal state distinction.
Secure development lifecycle practices can include state-machine validation and invariant checks that reduce incomplete internal state errors.
Explicit application security requirements can mandate state-transition validation and error-state handling.
Secure architecture principles encourage explicit state modelling and fail-safe transitions.
Secure coding standards can require defensive checks against invalid or ambiguous internal states.
Change-management procedures may indirectly catch state-related defects during release reviews.