CVE-2026-61612
Received Received - Intake

SSRF Bypass in CKAN MCP Server via DNS Resolution

Publication date: 2026-09-21

Last updated on: 2026-09-21

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-21
Last Modified
2026-09-21
Generated
2026-09-22
AI Q&A
2026-09-21
EPSS Evaluated
N/A
NVD
CVE-2026-61612
EUVD
EUVD-2026-84031

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-61612 is a Server-Side Request Forgery (SSRF) vulnerability in the CKAN MCP Server. The issue occurs because the validateServerUrl function only checks the hostname string and does not resolve DNS. This allows attacker-controlled server_url values with hostnames that resolve to internal IP addresses (like 127.0.0.1 or 169.254.169.254) to bypass security checks. The server then issues requests to loopback and cloud metadata services, exposing sensitive data.

Detection Guidance

To detect this SSRF vulnerability, monitor outbound HTTP requests from your CKAN MCP Server to internal or cloud metadata addresses like 127.0.0.1, 169.254.169.254, or RFC-1918 ranges. Check logs for requests to domains like lvh.me or *.nip.io which may resolve to internal IPs. Use network monitoring tools to inspect DNS resolution behavior of server_url parameters.

Impact Analysis

This vulnerability allows attackers to make the server send HTTP requests to internal systems or cloud metadata services. This could expose sensitive data like IAM credentials from cloud providers. In self-hosted setups, unauthenticated remote clients could directly trigger SSRF attacks.

Compliance Impact

This SSRF vulnerability could expose sensitive data like IAM credentials or internal network access, which may violate GDPR's data protection requirements for safeguarding personal data and HIPAA's controls for protecting health information. Unauthorized access to cloud metadata services (e.g., AWS IMDS) or internal systems could lead to breaches of confidentiality.

Mitigation Strategies

Upgrade to CKAN MCP Server version 0.4.108 or later which includes DNS resolution checks and IP validation. Set CKAN_ALLOWED_DOMAINS environment variable to restrict allowed domains for HTTP transport. Disable CKAN_HTTP_ALLOW_ALL unless absolutely necessary. Review and block requests to known problematic domains like lvh.me or *.nip.io in your firewall rules.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-61612. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart