# CVE-2026-100550: OpenClaw before 2026.8.1 Authentication Bypass via Access Group

> An authentication bypass in OpenClaw allows unauthorized Teams members to trigger agents when groupPolicy is set to allowlist.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-5m2m-2jqh-2wpg, GHSA-8938-r7c6-54vq, MINI-4v3p-w56w-cr99

## What is CVE-2026-100550?

CVE-2026-100550 is a medium-severity authentication bypass vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw (npm package 'openclaw') before 2026.8.1 contains an access-control bypass in the Microsoft Teams integration. When groupPolicy is set to allowlist, a missing or unsupported configured access group produces a denied group-resolution result that is not rejected by the final message-admission check, so a Teams member who is not on the allowlist can still trigger the configured agent despite the administrator's group boundary. The impact depends on the conversations, tools, and data available to that agent. The issue is fixed in version 2026.8.1.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100550 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100550 is a medium-severity authentication bypass vulnerability in OpenClaw, published on 26 Sep 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-100550 in the wild and no public exploit code.

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

## Sources

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

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