Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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-22171 is a high-severity Path Traversal (CWE-22) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th 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 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-22171, published on 2026-03-18, is a path traversal vulnerability (CWE-22) in OpenClaw versions prior to 2026.2.19. The flaw exists in the Feishu media download flow within the file extensions/feishu/src/media.ts, where untrusted media keys provided by Feishu are directly interpolated into temporary file paths based on os.tmpdir().
A remote, unauthenticated attacker (AV:N/AC:L/PR:N/UI:N) who can control Feishu media key values returned to the client can exploit this vulnerability by injecting traversal segments, such as "../", to escape the intended temporary directory. This allows the attacker to write arbitrary files within the permissions of the OpenClaw process, resulting in high confidentiality impact (C:H), low integrity impact (I:L), and no availability impact (A:N). The CVSS v3.1 base score is 8.2 with unchanged scope (S:U).
Mitigation is addressed in OpenClaw commits c821099157a9767d4df208c6b12f214946507871, cdb00fe2428000e7a08f9b7848784a0049176705, and ec232a9e2dff60f0e3d7e827a7c868db5254473f, with users advised to upgrade to version 2026.2.19 or later. Further details are provided in the GitHub security advisory at GHSA-vj3g-5px3-gr46 and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-path-traversal-in-feishu-media-temporary-file-naming.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12714
Vulnerability Data
OpenClaw versions prior to 2026.2.19 contain a path traversal vulnerability in the Feishu media download flow where untrusted media keys are interpolated directly into temporary file paths in extensions/feishu/src/media.ts. An attacker who can control Feishu media key values returned to…
more
the client can use traversal segments to escape os.tmpdir() and write arbitrary files within the OpenClaw process permissions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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 in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.