CVE-2026-41384
Openclaw ≤ 2026.3.24
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/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-41384 is a high-severity External Control of System or Configuration Setting (CWE-15) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception by PATH Environment Variable (T1574.007); ranked at the 4th 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 AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41384 is an environment variable injection vulnerability in OpenClaw versions before 2026.3.24. The flaw affects the CLI backend runner component, where attackers can inject malicious environment variables through workspace configuration files. This issue, published on 2026-04-28 and mapped to CWE-15, carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H).
A local attacker with no required privileges can exploit the vulnerability by crafting malicious workspace configurations. Exploitation requires user interaction, such as tricking a user into loading the tainted config. Successful attacks enable injection of arbitrary environment variables into backend process spawning, potentially resulting in code execution or sensitive data exposure.
Advisories recommend upgrading to OpenClaw 2026.3.24 or later to mitigate the issue. The fixing commit is available at https://github.com/openclaw/openclaw/commit/c2fb7f1948c3226732a630256b5179a60664ec24. Further details appear in the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-vfw7-6rhc-6xxg and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-environment-variable-injection-via-workspace-config-in-cli-backend.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26093
Vulnerability Data
OpenClaw before 2026.3.24 contains an environment variable injection vulnerability in the CLI backend runner that allows attackers to inject malicious environment variables through workspace configuration. Attackers can craft malicious workspace configs to inject arbitrary environment variables into the backend process…
more
spawning, enabling code execution or sensitive data exposure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access to configuration resources so external parties cannot alter them.
Enforces documented access restrictions on all changes to system configuration, directly blocking unauthorized external control of settings.
Limits privileges to the minimum needed, reducing the set of users who can externally modify configuration.
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.
Hardened configuration baselines and change controls directly limit external manipulation of settings.
Formal change and exception management catches externally driven configuration alterations.
Least-privilege access policies reduce unauthorized external modification of configuration values.
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.
Configuration management directly prevents external tampering with system settings.
Access rights assignment determines who may change system settings.
Privileged access rights reduce the number of users who can alter configuration.
Information access restriction limits who can view or modify configuration data.
Change management enforces controlled, authorized modifications to settings.
Access control policies underpin the technical restrictions on configuration changes.