Server-side Request Forgery (SSRF) Affecting @cardano402/mcp-server package, versions <0.1.2
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-CARDANO402MCPSERVER-17817066
- published4 Jul 2026
- disclosed26 Jun 2026
- creditMorganOnCode
Introduced: 26 Jun 2026
CVE NOT AVAILABLE CWE-22 (opens in a new tab)How to fix?
Upgrade @cardano402/mcp-server to version 0.1.2 or higher.
Overview
@cardano402/mcp-server is a MCP server that exposes paid HTTP endpoints as MCP tools, paying via the x402 Cardano scheme.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) through improper validation of catalog.server.url and insecure HTTP transport configuration. An attacker can access internal network resources or trigger unauthorized transactions by submitting crafted requests to the exposed HTTP interface or by supplying a malicious catalog with a manipulated server.url field. This is only exploitable if the server is run with --transport http on an untrusted network or pointed at untrusted catalogs.
Workaround
This vulnerability can be mitigated by running with --transport stdio (default), only using audited catalogs, using a low-balance hot wallet, and avoiding enabling MAINNET=true until the package is upgraded.