Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L/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-41347 is a low-severity CSRF (CWE-352) vulnerability in Openclaw Openclaw. Its CVSS base score is 2.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 1th 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 SC-23 (Session Authenticity) — 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-41347 is a cross-site request forgery (CSRF) vulnerability in OpenClaw versions before 2026.3.31, stemming from a lack of browser-origin validation in HTTP operator endpoints when the software operates in trusted-proxy mode (CWE-352). This flaw enables attackers to send malicious requests from a victim's browser to perform unauthorized actions on those endpoints. The vulnerability carries a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) and was published on 2026-04-23.
Any remote attacker can exploit this issue without privileges by crafting malicious web content, such as a webpage or email link, that tricks an authenticated user into interacting with it via their browser in a trusted-proxy OpenClaw deployment. User interaction is required, but the low attack complexity and network accessibility make it feasible. Exploitation allows limited unauthorized actions on HTTP operator endpoints, yielding low impacts to confidentiality, integrity, and availability, though the changed scope elevates the severity due to cross-origin effects.
Advisories recommend upgrading to OpenClaw 2026.3.31 or later, which addresses the issue through commit 6b3f99a11f4d070fa5ed2533abbb3d7329ea4f0d. Further mitigation details and analysis are available in the GitHub Security Advisory (GHSA-mhr7-2xmv-4c4q) and the VulnCheck advisory on the OpenClaw CSRF vulnerability.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25331
Vulnerability Data
OpenClaw before 2026.3.31 lacks browser-origin validation in HTTP operator endpoints when operating in trusted-proxy mode, allowing cross-site request forgery attacks. Attackers can exploit this by sending malicious requests from a browser in trusted-proxy deployments to perform unauthorized actions on HTTP…
more
operator endpoints.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
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 anti-CSRF controls such as tokens or SameSite attributes.
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.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.