CVE-2026-105140 obot-platform CVE debrief

Who should care

Defenders responsible for Obot deployments, particularly those using versions 0.25.0-0.25.5 and 0.26.0, should assess exposure and prioritize remediation. This includes verifying affected systems, applying patches, and reviewing auth provider group refresh configurations to prevent similar issues. Security teams and vulnerability management teams should also review the vulnerability and its potential impact on their environments.

Why it matters

CVE-2026-105140 is a low-severity vulnerability in Obot versions 0.25.0 before 0.25.6 and 0.26.0 before 0.26.1 that can restore revoked group memberships, allowing users to retain access for about ten minutes. Defenders should assess exposure, prioritize remediation, and verify affected systems.

• Verify affected Obot versions to prevent potential access restoration
• Apply patches to prevent potential access restoration
• Review auth provider group refresh configurations to prevent similar issues

Technical summary

A race condition in Obot's auth provider group refreshes can restore revoked group memberships, allowing users to retain access for about ten minutes. This occurs when overlapping refreshes for the same user commit out of order, persisting stale memberships. The vulnerability affects Obot versions 0.25.0 before 0.25.6 and 0.26.0 before 0.26.1. Defenders should prioritize verifying affected Obot versions and applying patches to prevent potential access restoration. The issue is specific to auth provider group refreshes and does not affect other Obot functionality.

Defensive priority

Defenders should prioritize verifying affected Obot versions and applying patches to prevent potential access restoration.

Recommended defensive actions

• Verify Obot versions 0.25.0-0.25.5 and 0.26.0 in use and apply patches
• Review auth provider group refresh configurations
• Monitor for potential access restoration
• Apply patches to prevent potential access restoration
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and patch commits. The vulnerability has been patched in Obot versions 0.25.6 and 0.26.1. Defenders should verify affected systems and apply patches to prevent potential access restoration. The source item and CVE record provide further information on the vulnerability and affected scope.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.