CVE-2026-43572: OpenClaw · Microsoft Teams SSO invoke handler missed sender authorization checks
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.4.14 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.14
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in openclaw CLI version 2026.4.14 and later. Users should upgrade to version 2026.4.14 or newer to remediate this issue. No additional mitigation steps are required once the upgrade is applied.
Description
A vulnerability in the openclaw CLI package affects Microsoft Teams SSO invoke handler, which missed sender authorization checks. This flaw allows processing of SSO signin invokes from senders without applying the usual allowlist checks. Versions from 2026.4.10 up to but not including 2026.4.14 are affected. The issue was fixed in version 2026.4.14 by routing SSO invoke handling through the proper Teams sender authorization path and adding coverage for denied senders. Users should upgrade to version 2026.4.14 or later to remediate this vulnerability.