CVE
Obot access token theft via OAuth resource metadata
Only affects Obot 0.26.0 through 0.26.3 when users connect to remote MCP servers that use OAuth. Fixed in Obot 0.27.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.27.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Obot versions 0.26.0 through 0.26.3 are affected. Users connect to remote MCP servers that use OAuth. The remote MCP server is malicious or compromised. The attacker's authorization server accepts Obot as a client via open client registration or client ID metadata documents, and honors RFC 8707 resource indicators. The victim approves or has previously approved the consent prompt from that authorization server.
Summary
Obot, an open-source platform, is affected by a flaw in how it handles OAuth resource metadata from remote MCP servers. A malicious MCP server can remotely trick Obot into sending a victim's access token to the attacker, though the victim must take some action to trigger it.
Original description
Obot from 0.26.0 before 0.27.0 fails to validate the resource identifier in remote MCP server protected resource metadata, allowing malicious MCP servers to steal access tokens. Attackers can name a different service and authorization server with chosen scopes, causing Obot to obtain the victim's token for that service and forward it to the attacker.
Who should check
Teams running Obot 0.26.0 through 0.26.3 that let users connect to remote MCP servers using OAuth
“You are affected if you run Obot >= v0.26.0, <= v0.26.3 and users connect to remote MCP servers that use OAuth”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Go packages
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Obot versions 0.26.0 through 0.26.3 are affected. Users connect to remote MCP servers that use OAuth. The remote MCP server is malicious or compromised. The attacker's authorization server accepts Obot as a client via open client registration or client ID metadata documents, and honors RFC 8707 resource indicators. The victim approves or has previously approved the consent prompt from that authorization server.Upgrade to a fixed version: 0.27.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130766 (Obot 0.26.0 before 0.27.0 Access Token Theft via OAuth Resource Metadata), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130766 (entry last updated 2026-11-18):
Affected:
- Go package github.com/obot-platform/obot: from 0.26.0, fixed in 0.27.0
Fixed versions: 0.27.0.
Conditions (all must be true for the bug to be hit):
- Obot versions 0.26.0 through 0.26.3 are affected. (source: https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6)
- Users connect to remote MCP servers that use OAuth. (source: https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6)
- The remote MCP server is malicious or compromised. (source: https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6)
- The attacker's authorization server accepts Obot as a client via open client registration or client ID metadata documents, and honors RFC 8707 resource indicators. (source: https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6)
- The victim approves or has previously approved the consent prompt from that authorization server. (source: https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-130766 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130766 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/obot-platform/obot/security/advisories/GHSA-x3hf-v55x-jcp6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130766
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130766"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
From 0.26.0 · fixed in 0.27.0
Fixed in v0.27.0 (released Oct 20, 2026, 29 days before disclosure).
The latest release, v0.28.1, is not affected.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · obot-platform/obot · Advisory GHSA-x3hf-v55x-jcp6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130766 |
| Record | NVD · CVE-2026-130766 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130766
Is CVE-2026-130766 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A malicious or compromised remote MCP server can get Obot to hand over a valid access token issued to the victim for another service protected by the same authorization server, with attacker-chosen scopes.Source: github.com
Which versions are affected by CVE-2026-130766?
github.com/obot-platform/obot (Go): from 0.26.0 before 0.27.0.Source: cve.now feed data
Am I affected, and how do I check?
Obot versions 0.26.0 through 0.26.3 are affected when users connect to remote MCP servers that use OAuth. Check the installed Obot version against that range and whether any remote MCP server using OAuth is connected. The attack also needs an authorization server that accepts Obot as a client via open client registration or client ID metadata documents and honors RFC 8707 resource indicators, and a victim who approves the consent prompt.Source: github.com
How do I fix CVE-2026-130766?
Upgrade Obot to 0.27.0, which is the fixed version in the affected range.Source: github.com