CVE-2026-73845 in ckan-mcp-server
Summary
by MITRE • 08/14/2026
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, the ckan_get_mqa_quality and ckan_get_mqa_quality_details tools in src/tools/quality.ts use isValidMqaServer to validate the server_url parameter with a prefix-only regular expression for dati.gov.it, allowing suffix-host and URL-userinfo values to target an attacker-controlled host and return a spoofed response. This issue is fixed in version 0.4.112.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/14/2026
The CKAN MCP Server represents a critical infrastructure component designed for querying CKAN open data portals, serving as a bridge between data consumers and government datasets hosted on platforms like dati.gov.it. This toolset includes specialized utilities such as ckan_get_mqa_quality and ckan_get_mqa_quality_details that are specifically engineered to retrieve quality metrics from CKAN repositories. The vulnerability stems from improper input validation mechanisms within the quality assessment tools, particularly in the isValidMqaServer function located in src/tools/quality.ts. This function employs a flawed prefix-only regular expression pattern that inadequately validates server_url parameters, creating a significant security gap that could be exploited by malicious actors.
The technical flaw manifests through an insufficient validation approach that relies solely on prefix matching rather than comprehensive URL parsing and verification. When processing server_url inputs, the isValidMqaServer function accepts any string that begins with dati.gov.it as valid, completely ignoring potential suffix-host variations or userinfo components that could redirect requests to attacker-controlled servers. This vulnerability creates a path for server-side request forgery attacks where an adversary can manipulate the URL structure to bypass intended validation checks, potentially routing queries through malicious endpoints while maintaining the appearance of legitimate communication with dati.gov.it infrastructure.
The operational impact of this vulnerability extends beyond simple data integrity concerns, as it enables sophisticated attack vectors that could compromise data authenticity and system security. An attacker could craft malicious URLs that pass the prefix validation while redirecting requests to their own servers, potentially intercepting sensitive data or returning spoofed quality metrics that mislead users about dataset reliability. This issue particularly affects government data portals where trust in information accuracy is paramount, as it undermines the integrity of quality assessment processes and could be exploited to manipulate perceptions about data quality metrics.
The security implications align with common CWE classifications related to input validation failures and server-side request forgery vulnerabilities, specifically mapping to CWE-20 for improper input validation and CWE-918 for server-side request forgery. This vulnerability also corresponds to ATT&CK technique T1190 for exploit public-facing application, as it represents an accessible entry point through the quality assessment tooling. The fix implemented in version 0.4.112 addresses this by replacing the inadequate prefix-only validation with more robust URL parsing and validation mechanisms that properly examine the complete URL structure rather than relying on superficial pattern matching.
Mitigation strategies should focus on implementing comprehensive input validation that examines all components of URLs including protocol, host, port, path, and userinfo sections rather than relying on simple prefix matching. Organizations should also consider implementing additional security controls such as network segmentation, API rate limiting, and enhanced monitoring for unusual query patterns that might indicate exploitation attempts. Regular security assessments of tooling components and input validation mechanisms are essential to prevent similar issues from emerging in other parts of the system architecture. The vulnerability serves as a reminder of the critical importance of thorough URL validation in applications that process external inputs, particularly those interacting with government data repositories where data integrity and authenticity are fundamental requirements.