CVE-2026-61612: @aborruso/ckan-mcp-server has SSRF via DNS-name → internal IP — incomplete fix of CVE-2026-53509
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 serverurl 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@aborruso/ckan-mcp-serverto a version that resolves this vulnerability.Fixed in 0.4.108
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using versions prior to 0.4.108 are affected when a caller can supply the server_url value. The issue applies even when the supplied hostname appears non-internal, if its DNS resolution points to an internal address.
What access does an attacker need to exploit this?
An attacker needs low-privileged access and user interaction, as reflected by the CVSS vector, plus the ability to cause a caller-supplied server_url to be used. Exploitation relies on providing a DNS name that resolves to loopback or an internal address, including the cloud metadata address 169.254.169.254.
What is the remediation?
Upgrade @aborruso/ckan-mcp-server to version 0.4.108, which contains the updated fix. Earlier validation checked only the hostname string and did not resolve DNS.