CVE
Obot SSRF in OAuth token endpoint handling
Affects Obot 0.8.0 through 0.26.3 for accounts that can add remote MCP servers (Power User or higher). 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 version 0.8.0 up to and including 0.26.3 (affected versions >= v0.8.0, <= v0.26.3). Attacker needs an account that can add remote MCP servers (Power User or higher).
Summary
Obot contains a server-side request forgery flaw. An attacker with a Power User account can remotely make the server send token exchange or refresh requests, including redirected GET requests, to internal hosts or cloud metadata services by advertising a malicious OAuth token endpoint in remote MCP server metadata, and can read the error response bodies.
Original description
Obot from 0.8.0 before 0.27.0 contains a server-side request forgery vulnerability that allows Power User accounts to reach internal hosts by advertising a malicious OAuth token endpoint in remote MCP server metadata. Attackers can direct token exchange or refresh requests, including redirected GET requests, to cloud metadata services or private-network hosts and read error response bodies.
Who should check
Teams running Obot (obot-platform/obot, Go) version 0.8.0 through 0.26.3 that let Power User or higher accounts add remote MCP servers.
“You are affected if you run Obot <= v0.26.3 .”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 33 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Obot version 0.8.0 up to and including 0.26.3 (affected versions >= v0.8.0, <= v0.26.3). Attacker needs an account that can add remote MCP servers (Power User or higher).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-130764 (Obot 0.8.0 before 0.27.0 SSRF via OAuth Token Endpoint), 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-130764 (entry last updated 2026-11-18):
Affected:
- Go package github.com/obot-platform/obot: from 0.8.0, fixed in 0.27.0
Fixed versions: 0.27.0.
Conditions (all must be true for the bug to be hit):
- Obot version 0.8.0 up to and including 0.26.3 (affected versions >= v0.8.0, <= v0.26.3). (source: https://github.com/obot-platform/obot/security/advisories/GHSA-57qx-69p6-3w3g)
- Attacker needs an account that can add remote MCP servers (Power User or higher). (source: https://github.com/obot-platform/obot/security/advisories/GHSA-57qx-69p6-3w3g)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130764 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130764 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-57qx-69p6-3w3g
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-130764
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-130764"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
From 0.8.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-57qx-69p6-3w3g |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130764 |
| Record | NVD · CVE-2026-130764 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130764
Is CVE-2026-130764 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?
An attacker can make the Obot server send requests to hosts on its internal network or to a cloud instance metadata service. The attacker can read the response body of non-success responses in the returned error, and redirects can cause GET requests to internal addresses.Source: github.com
Which versions are affected by CVE-2026-130764?
github.com/obot-platform/obot (Go): from 0.8.0 before 0.27.0.Source: cve.now feed data
How do I fix CVE-2026-130764?
Upgrade Obot to version 0.27.0 or later, which is the fixed version for this range.Source: github.com