CVE-2026-61612 @aborruso/ckan-mcp-server has SSRF via DNS-name → internal IP — incomplete fix of CVE-2026-53509
Attackers can bypass SSRF guards via DNS resolution to access internal services and cloud metadata, requiring an upgrade to the CKAN MCP Server library.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-61612?
CVE-2026-61612 is a medium-severity server-side request forgery vulnerability in ondata ckan-mcp-server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to version 0.4.108, the SSRF guard `validateServerUrl` (added for CVE-2026-33060, extended for CVE-2026-53509) validates only the hostname string and never resolves DNS. Any caller-supplied `server_url` whose hostname *resolves* to an internal address passes the guard, so the server issues requests to loopback and cloud metadata (`169.254.169.254`). This is a third bypass of the same guard, and it reaches IMDS — strictly more than CVE-2026-53509, which only reached loopback. Version 0.4.108 contains an updated fix.
Weakness: CWE-918
Which versions are affected by CVE-2026-61612?
2 open source packages ship an affected version, including @aborruso/ckan-mcp-server.
| Package | Affected | Fixed in |
|---|---|---|
@aborruso/ckan-mcp-server npm | All versions | 0.4.108 |
@aborruso/ckan-mcp-server npm | All versions | 0.4.108 |
How do I fix CVE-2026-61612?
Upgrade @aborruso/ckan-mcp-server to 0.4.108 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-61612 being exploited?
There is no known exploitation of CVE-2026-61612 in the wild and no public exploit code.
Sources
Also known as GHSA-798p-78g2-v556.