# CVE-2026-100553: OpenClaw 2026.6.9 before 2026.8.1 Cross-Context Policy Bypass via Feishu unpin

> Authenticated users can bypass cross-context policy restrictions to remove pins from other Feishu groups when specific security settings are disabled.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 29 Sep 2026
- **Also known as:** GHSA-9w3x-7vmw-xp4x, GHSA-h9jh-75j7-7hhx, MINI-hj4h-qg3v-v39h

## What is CVE-2026-100553?

CVE-2026-100553 is a medium-severity 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 versions >= 2026.6.9 and < 2026.8.1 do not declare the native chatId parameter as a delivery target in the Feishu unpin feature, so unpin requests can bypass the shared same-provider cross-context target check. When tools.message.crossContext.allowWithinProvider is disabled, an admitted (authenticated) sender can remove a pin from another Feishu group that the sender and the configured account are otherwise permitted to access, bypassing the intended cross-context message mutation policy. Feishu membership and group authorization still apply, and the demonstrated impact is limited to message mutation (pin removal). The issue is fixed in 2026.8.1.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100553 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100553 is a medium-severity 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-100553 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-100553/ (Markdown: https://insights.sbomify.com/CVE-2026-100553/index.md)
```

## Sources

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

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