# CVE-2026-43572: OpenClaw 2026.4.10 < 2026.4.14 - Missing Sender Authorization in Microsoft Teams SSO Invoke Handler

> Attackers can bypass sender authorization in OpenClaw's Microsoft Teams SSO handler, gaining unauthorized access to signin functionality.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-gc9r-867r-j85f, MINI-c84g-g43v-j79j

## What is CVE-2026-43572?

CVE-2026-43572 is a medium-severity missing authorization vulnerability in Openclaw Openclaw, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw versions 2026.4.10 before 2026.4.14 contain a missing authorization vulnerability in the Microsoft Teams SSO invoke handler that fails to apply sender allowlist checks. Attackers can bypass sender authorization by sending SSO invoke requests that are processed without proper validation, allowing unauthorized access to Teams SSO signin functionality.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-43572?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | From 2026.4.10 | 2026.4.14 |
| `openclaw` | npm | From 2026.4.10 | 2026.4.14 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-43572?

Upgrade openclaw to 2026.4.14 or later.

## Is CVE-2026-43572 being exploited?

There is no known exploitation of CVE-2026-43572 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43572 and fix it if it is affected.

What it is: CVE-2026-43572 is a medium-severity missing authorization vulnerability in Openclaw Openclaw, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43572 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected from 2026.4.10; fixed in 2026.4.14
- openclaw (npm): affected from 2026.4.10; fixed in 2026.4.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43572/ (Markdown: https://insights.sbomify.com/CVE-2026-43572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43572
- OSV: https://osv.dev/vulnerability/CVE-2026-43572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43572/
Summaries are generated and may contain mistakes; the official description above is the record.