CVE-2026-32017
Openclaw ≤ 2026.2.19
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/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-32017 is a medium-severity Incomplete List of Disallowed Inputs (CWE-184) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 17th 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 SI-10 (Information Input Validation) — 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-32017 is an allowlist bypass vulnerability in the exec safeBins policy of OpenClaw versions prior to 2026.2.19. The flaw enables attackers to write arbitrary files by attaching short-option payloads, such as -o, to whitelisted binaries, thereby circumventing argument validation checks that are intended to block unauthorized file-write operations. This issue is classified under CWE-184 (Incomplete List of Disallowed Inputs) with a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L), indicating high integrity impact potential over the network with low privileges required.
Attackers with low-privilege access (PR:L) can exploit this vulnerability remotely (AV:N) with low complexity (AC:L) and no user interaction (UI:N). By appending short options to arguments of safeBins-whitelisted binaries, they bypass the policy's restrictions, achieving unauthorized arbitrary file writes that compromise system integrity (I:H) and cause limited availability disruption (A:L), without affecting confidentiality.
Mitigation is addressed in OpenClaw version 2026.2.19 and later through patches detailed in GitHub commits bafdbb6f112409a65decd3d4e7350fbd637c7754, cfe8457a0f4aae5324daec261d3b0aad1461a4bc, and fec48a5006eab37c6a5821726ccaeec886486b13. Additional guidance is available in the project's security advisory at GHSA-3x3x-h76w-hp98 and VulnCheck's advisory on the short-option bypass. Security practitioners should upgrade affected installations immediately and review exec safeBins configurations for similar bypass risks.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13283
Vulnerability Data
OpenClaw versions prior to 2026.2.19 contain an allowlist bypass vulnerability in the exec safeBins policy that allows attackers to write arbitrary files using short-option payloads. Attackers can bypass argument validation by attaching short options like -o to whitelisted binaries, enabling…
more
unauthorized file-write operations that should be denied by safeBins checks.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
V3.5.2V4.4.2V16.2.5
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on inputs, which structurally replaces incomplete deny-lists with complete allow-list or sanitization logic.
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 SDLC practices directly require complete, positive input validation instead of incomplete denylists.
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 discover missing input checks, but does not prevent the weakness during development.
Application security requirements can mandate complete input validation rules, but the control itself does not prescribe how to build those rules.
Secure architecture principles include robust input validation design, yet the control is broader than this single weakness.
Secure coding standards directly require exhaustive allow-lists or complete deny-lists for inputs, addressing the root cause of incomplete disallowed-input lists.