# CVE-2026-86122: Rowboat through 0.9.1 Server-Side Request Forgery via Custom MCP Server

> Authenticated users can exploit unvalidated URLs in Rowboat to access internal services and cloud metadata, enabling network enumeration and data theft.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jmxm-qmrf-xrpp

## What is CVE-2026-86122?

CVE-2026-86122 is a medium-severity server-side request forgery vulnerability in rowboatlabs rowboat, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rowboat through 0.9.1 fails to validate custom MCP server and webhook URLs, allowing authenticated users to configure arbitrary destinations. Attackers can point these URLs at internal services and cloud metadata endpoints to perform server-side request forgery and enumerate internal network topology.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

No fix has been published for CVE-2026-86122 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86122 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86122 is a medium-severity server-side request forgery vulnerability in rowboatlabs rowboat, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86122 in the wild and no public exploit code.

Affected product: rowboatlabs rowboat. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-86122/ (Markdown: https://insights.sbomify.com/CVE-2026-86122/index.md)
```

## Sources

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

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