# CVE-2026-130768: Obot 0.14.0 before 0.27.0 SSRF Protection Bypass via MCP Server URLs


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-mj55-384p-p7w5, GHSA-r3m3-5rmh-h3fm

## What is CVE-2026-130768?

CVE-2026-130768 is a medium-severity vulnerability in obot-platform obot, published on 18 Nov 2026. 

### Official description

Obot from 0.14.0 before 0.27.0 contains a server-side request forgery vulnerability that allows Power Users to bypass outbound protections by supplying unspecified addresses, IPv6 transition addresses, or registry icon URLs. Attackers can add remote MCP servers pointing to 0.0.0.0, ::, or NAT64/6to4/Teredo addresses embedding blocked IPv4 addresses to probe internal services for reachability.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-130768?

1 open source package ship an affected version, including github.com/obot-platform/obot.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/obot-platform/obot` | Go | `pkg:golang/github.com/obot-platform/obot` | From 0.14.0 | 0.27.0 |

## How do I fix CVE-2026-130768?

Upgrade github.com/obot-platform/obot to 0.27.0 or later.

## Is CVE-2026-130768 being exploited?

There is no known exploitation of CVE-2026-130768 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130768 and fix it if it is affected.

What it is: CVE-2026-130768 is a medium-severity vulnerability in obot-platform obot, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130768 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/obot-platform/obot (Go): affected from 0.14.0; fixed in 0.27.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130768/ (Markdown: https://insights.sbomify.com/CVE-2026-130768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130768
- OSV: https://osv.dev/vulnerability/CVE-2026-130768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130768/
Summaries are generated and may contain mistakes; the official description above is the record.
