Is CVE-2026-101064 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101064 being exploited in the wild.

How severe is CVE-2026-101064?

High severity, with a CVSS score of 7.6, published 27 September 2026.

Which products and versions are affected?

github.com/obot-platform/obot (Go) SEMVER:introduced=0,fixed=0.23.0; Obot Platform Obot before v0.23.0.

Is there a fix for CVE-2026-101064?

Yes. github.com/obot-platform/obot (Go): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101064 attacked?

It is attacked over the network.

Am I affected by CVE-2026-101064?

Check whether you run github.com/obot-platform/obot (Go) or Obot Platform Obot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101064: Obot server-side request forgery in remote MCP server registration

CVE-2026-101064 · Severity: high · CVSS 7.6 · Published 2026-09-27

Obot, an automation platform, fails to validate URLs when users register remote MCP servers, allowing attackers with privileged roles (Power User or higher) to force the server to make requests to internal services and cloud metadata endpoints. An attacker could exploit this to steal cloud credentials and other sensitive secrets exposed in error messages, potentially compromising the entire cloud account.

Technologies: github.com/obot-platform/obot (Go), Obot Platform Obot. Vendors: Go, Obot Platform.

Quick answers

Is CVE-2026-101064 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101064 being exploited in the wild.
How severe is CVE-2026-101064?: High severity, with a CVSS score of 7.6, published 27 September 2026.
Which products and versions are affected?: github.com/obot-platform/obot (Go) SEMVER:introduced=0,fixed=0.23.0; Obot Platform Obot before v0.23.0.
Is there a fix for CVE-2026-101064?: Yes. github.com/obot-platform/obot (Go): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101064 attacked?: It is attacked over the network.
Am I affected by CVE-2026-101064?: Check whether you run github.com/obot-platform/obot (Go) or Obot Platform Obot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/obot-platform/obot (Go): upgrade to 0.23.0 or later
```
go get github.com/obot-platform/obot@v0.23.0
```

Technical details

The vulnerability is a non-blind server-side request forgery (SSRF) in the remote MCP server registration flow. Privileged users can specify arbitrary URLs without destination validation, and Obot automatically fetches OAuth metadata from these URLs during reconciliation. The response body is reflected in error messages, allowing credential disclosure from internal services and the cloud metadata endpoint (169.254.169.254).

Affected products

Obot Platform Obot before v0.23.0

Identifiers

CVE-2026-101064
GO-2026-6522

Timeline

2026-06-22: disclosed
2026-06-22: patched: v0.23.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.