OpenClaw CVE-2026-41365

Exploitation requires authentication to OpenClaw (CVSS PR:L) - the attacker must have valid user credentials or session access to the application. Additionally, the target organization must have configured sender allowlists within OpenClaw's Teams integration; organizations without active allowlist policies are not impacted. The vulnerability specifically affects message retrieval via Graph API thread history endpoints, so configurations that disable thread history access or do not use Graph API integration are unaffected. Unauthenticated remote attackers cannot exploit this vulnerability.

CVSS 5.3 (Medium severity) with network attack vector and low complexity reflects the moderate real-world risk. The CVSS vector shows authentication required (PR:L), limiting the attack surface to users with legitimate OpenClaw access, and confidentiality impact is low (VC:L) rather than complete compromise. However, the practical risk depends heavily on: (1) how OpenClaw's sender allowlists are deployed in target organizations (if they are critical for data governance or compliance, impact escalates), and (2) whether sensitive sender communications are consistently blocked via these filters. The authentication requirement significantly reduces attack surface compared to unauthenticated scenarios. No EPSS score, KEV status, or public POC data were provided, suggesting this is a disclosed but not widely exploited vulnerability at the time of patching. The core issue - authorization bypass - is a critical vulnerability class despite the moderate CVSS score, as it directly undermines access control mechanisms organizations rely on for data protection.

An authenticated OpenClaw user with legitimate access to the application can retrieve Teams thread history messages that organizational policy restricts via sender allowlists. By making requests to the underlying Microsoft Graph API endpoints proxied through OpenClaw, the attacker bypasses the intended filter and gains access to sensitive communications from restricted senders, potentially exposing confidential project details, executive communications, or other protected information that should have been hidden by the allowlist policy.