Is there a patch available for CVE-2026-62205?

Yes, a patch is available for CVE-2026-62205. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-62205

Q: What is the CVSS score of CVE-2026-62205?

CVE-2026-62205 has a CVSS 4.0 base score of 6.0 (Medium). CVSS 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:X. EPSS exploitation probability: 0.2%.

EUVD-2026-45093 MEDIUM

Missing Authorization (CWE-862)

2026-07-17 VulnCheck

GHSA-q7vf-83cx-xc54

Authentication Bypass Openclaw

6.0

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

6.0 MEDIUM

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:X

vuln.today AI

5.9 MEDIUM

AC:H reflects AT:P - MS Teams feature must be enabled and reachable; PR:L per authenticated lower-trust caller; no confidentiality impact; low availability impact per description.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 17, 2026 - 02:32 EUVD

Analysis Generated

Jul 17, 2026 - 01:08 vuln.today

DescriptionCVE.org

OpenClaw versions 2026.4.12-beta.1 before 2026.6.6 contain a missing-authorization vulnerability in the MS Teams message actions feature. When the affected feature is enabled and reachable, a lower-trust caller or a configured input path can perform actions that should have required a stronger authorization or policy check. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path. The issue is fixed in 2026.6.6.

AnalysisAI

Missing authorization controls in OpenClaw's MS Teams message actions feature permit a low-privilege authenticated caller to invoke operations that should require elevated permissions or policy checks, resulting in high integrity impact (VI:H per the CVSS 4.0 vector) on affected deployments. The flaw spans versions 2026.4.12-beta.1 through 2026.6.5, and practical severity is configuration-dependent - exploitation is gated on the MS Teams feature being enabled and reachable. No public exploit code exists and the vulnerability is not in the CISA KEV catalog; the vendor confirmed and patched the issue in 2026.6.6.

Technical ContextAI

OpenClaw is a software application exposing an MS Teams message actions integration, identified via CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*. The root cause is CWE-862 (Missing Authorization): the message actions code path fails to enforce a sufficiently strong authorization or policy check before executing privileged operations, allowing a lower-trust caller to traverse that path without adequate entitlement verification. The CVSS 4.0 vector encodes AT:P (Attack Requirements: Present), confirming that the flaw is not exposed in all deployments - the MS Teams feature must be enabled and the endpoint must be reachable for exploitation to be feasible. The impact is bounded to the vulnerable system (SC:N/SI:N/SA:N), with no lateral scope change to subsequent systems.

RemediationAI

Upgrade to OpenClaw 2026.6.6, the vendor-confirmed fixed release per the GitHub security advisory (https://github.com/openclaw/openclaw/security/advisories/GHSA-p5xh-frrh-cmgj). If immediate patching is not possible, the most direct compensating control is to disable the MS Teams message actions feature entirely, since exploitation requires that feature to be enabled and reachable - disabling it eliminates the vulnerable code path at the cost of losing Teams integration functionality. Where disabling is not acceptable, network-layer access controls (firewall rules or reverse-proxy allowlists) restricting which callers can reach the message actions endpoint reduce exposure, though they do not address the underlying authorization flaw. No additional workarounds are documented in the available references.