CVE-2026-86122: Rowboat through 0.9.1 Server-Side Request Forgery via Custom MCP Server
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Rowboatto a version that resolves this vulnerability.Fixed in 0.9.1 - Configuration
Ensure Rowboat validates custom MCP server and webhook URLs to prevent authenticated users from configuring arbitrary destinations that enable SSRF and internal network topology enumeration.
Rowboat custom MCP server and webhook URL validation = enabled
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs to be authenticated and able to configure a custom MCP server or webhook URL. The vulnerable behavior allows that user to direct server-side requests to arbitrary destinations.
What systems are at risk from the SSRF requests?
Internal services and cloud metadata endpoints are specifically at risk. An attacker may use the server as a proxy to reach those destinations and enumerate internal network topology.
Are default deployments affected?
The available information does not establish whether custom MCP server or webhook configuration is enabled or accessible by default. Exposure depends on whether authenticated users can configure these URLs.
What can be done if an update is not immediately available?
Restrict the ability to configure custom MCP server and webhook URLs to trusted administrators, and prevent the Rowboat server from reaching internal-only services and cloud metadata endpoints where possible.