# CVE-2026-62224: OpenClaw MS Teams < 2026.5.12 Authorization Bypass

> Attackers can bypass authorization controls in OpenClaw MS Teams by exploiting mutable display name bindings to perform unauthorized actions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-7w4v-g4m6-j88v, GHSA-fjfc-7x5g-g52w, MINI-5w56-q4jc-j8rj

## What is CVE-2026-62224?

CVE-2026-62224 is a low-severity authentication bypass vulnerability in openclaw msteams, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw MS Teams before 2026.5.12 contain an authorization bypass vulnerability where the allowFrom feature binds to mutable display names. Attackers with lower-trust access can perform actions requiring stronger authorization by exploiting the mutable display name binding in the affected feature.

Weakness: CWE-863 (Incorrect Authorization), CWE-290 (Authentication Bypass by Spoofing)

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


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

Upgrade to a fixed version.

## Is CVE-2026-62224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62224 is a low-severity authentication bypass vulnerability in openclaw msteams, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62224 in the wild and no public exploit code.

Affected product: openclaw msteams. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-62224/ (Markdown: https://insights.sbomify.com/CVE-2026-62224/index.md)
```

## Sources

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

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