Skip to main content
VulnerabilityPublished

CVE-2026-101064: obot · Server-Side Request Forgery (SSRF)

Affects obotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 0.23.0 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.23.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade obot and obot-platform/obot to 0.23.0.

Affected software

ProductAffectedFixed in
obot-platformobotAffected
  • <0.23.0
Fixed in
  • 0.23.0
GitHubobot-platform/obotpkg:github/obot-platform/obotOther threatsAffected
  • <0.23.0
Fixed in
  • 0.23.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in obot version 0.23.0. Users should upgrade to version 0.23.0 or later to remediate this vulnerability. Until then, restrict Power User or higher roles to trusted personnel only and monitor for suspicious activity related to remote MCP server registration.

Description

Obot before v0.23.0 contains a server-side request forgery vulnerability in remote MCP server registration that allows privileged users to specify arbitrary URLs without destination validation. Attackers with Power User or higher roles can coerce Obot to make requests to internal services and cloud metadata endpoints, reading responses in error messages to disclose sensitive credentials.

References

Community reviews

Loading reviews…