CVE-2026-41294
Openclaw ≤ 2026.3.28
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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-41294 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 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 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-41294 affects OpenClaw versions before 2026.3.28, enabling environment variable injection due to the application loading a .env file from the current working directory prior to trusted state-dir configuration. This flaw allows override of runtime configuration and security-sensitive environment settings during OpenClaw startup, as documented in the CVE description published on 2026-04-21. The vulnerability carries a CVSS v3.1 base score of 8.6 (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) and maps to CWE-15 (External Control of System or Configuration Setting).
Attackers with local access can exploit this by placing a malicious .env file in a repository or workspace directory. Exploitation requires low complexity and no privileges but depends on user interaction, such as a user invoking OpenClaw from the compromised directory. Successful injection alters critical environment variables, achieving high impacts on confidentiality, integrity, and availability with a changed scope.
Mitigation details are outlined in advisories at https://github.com/openclaw/openclaw/security/advisories/GHSA-8rh7-6779-cjqq and https://www.vulncheck.com/advisories/openclaw-environment-variable-injection-via-cwd-env-file. OpenClaw 2026.3.28 addresses the issue by correcting the .env loading order relative to trusted configuration.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23998
Vulnerability Data
OpenClaw before 2026.3.28 loads the current working directory .env file before trusted state-dir configuration, allowing environment variable injection. Attackers can place a malicious .env file in a repository or workspace to override runtime configuration and security-sensitive environment settings during OpenClaw…
more
startup.
- 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.
Formal change and exception management catches externally driven configuration alterations.
Least-privilege access policies reduce unauthorized external modification of configuration values.
Hardened configuration baselines and change controls directly limit external manipulation of 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.
Access control policies underpin the technical restrictions on configuration changes.
Access rights assignment determines who may change system settings.
Documented operating procedures define how configuration changes must be performed.
Use of privileged utility programs is controlled to prevent misuse of configuration tools.
Restricting software installation limits unauthorized changes to configuration.
Privileged access rights reduce the number of users who can alter configuration.