# CVE-2026-105140: Obot 0.25.0 before 0.25.6 and 0.26.0 before 0.26.1 Race Condition Restores Revoked Group Membership

> A race condition in Obot allows attackers to retain revoked group-based access for ten minutes by exploiting out-of-order auth provider refreshes.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/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:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-929v-v9hq-5xhr

## What is CVE-2026-105140?

CVE-2026-105140 is a low-severity vulnerability in obot-platform obot, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Obot 0.25.0 before 0.25.6 and 0.26.0 before 0.26.1 contains a race condition in auth provider group refreshes that can restore group memberships just revoked in the identity provider. When overlapping refreshes for the same user commit out of order, stale memberships are persisted and the user retains revoked group-based access for about ten minutes.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

No fix has been published for CVE-2026-105140 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105140 is a low-severity vulnerability in obot-platform obot, published on 7 Oct 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-105140 in the wild and no public exploit code.

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

## Sources

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

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