NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
HIGH severity

CVE-2026-130764 — OBOT

HIGH

CVE-2026-130764 is a high-severity (CVSS 7.6) Server-Side Request Forgery (SSRF) vulnerability in obot-platform obot. A fix is available — see the affected versions and patch details below.

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…

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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.

Affected Products

1 product · 1 configurations
Application
obotobot-platform
< 0.27.0
1 version
0.8.0

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every obot-platform obot deployment and check each version against the affected-products list above.

  2. Fix

    Apply the obot-platform obot security patch or hotfix for CVE-2026-130764 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2026-130764 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

CVE-2026-130764: OBOT SSRF (High 7.6)