CVE-2026-41330
Openclaw ≤ 2026.3.31
Raw vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/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-41330 is a low-severity Insecure Default Variable Initialization (CWE-453) vulnerability in Openclaw Openclaw. Its CVSS base score is 2.0 (Low).
Operationally, ranked at the 3th 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-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24018
Vulnerability Data
OpenClaw before 2026.3.31 contains an environment variable override vulnerability in host exec policy that fails to properly enforce proxy, TLS, Docker, and Git TLS controls. Attackers can bypass security controls by overriding environment variables to circumvent proxy settings, TLS verification,…
more
Docker restrictions, and Git TLS enforcement.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Requires establishing the most restrictive configuration settings, which directly overrides or prevents use of insecure default variable initializations.
Requires maintaining a documented baseline configuration that can enforce secure initial values instead of insecure defaults.
Mandates application of security engineering principles during development that include use of secure defaults and proper variable initialization.
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 insecure defaults but does not prevent them.
Configuration management enforces secure default values and prevents insecure initialization.
Secure development life cycle requires explicit secure initialization of variables.
Secure architecture principles include avoiding insecure defaults in design.
Secure coding standards mandate explicit, safe variable initialization.