CVE-2026-73845 ondata CVE debrief

Who should care

Defenders responsible for CKAN MCP Server instances should assess exposure and prioritize upgrading to version 0.4.112 or later. Roles responsible for maintaining CKAN MCP Server instances should verify server_url parameter validation and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

Defenders should care about this vulnerability as it allows for spoofed responses, potentially impacting the integrity of data returned by CKAN MCP Server instances. Roles responsible for maintaining CKAN MCP Server instances should assess exposure and prioritize upgrading to version 0.4.112 or later. The operational impact includes the potential for spoofed responses, the need to verify server_url parameter validation, and the priority on upgrading to the fixed version.

• Potential for spoofed responses
• Need to verify server_url parameter validation
• Priority on upgrading to fixed version

Technical summary

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 impacts data integrity and defenders should assess exposure and prioritize upgrading to version 0.4.112 or later. The vulnerability class involves improper validation of user input, and the likely operational impact includes potential for spoofed responses.

Defensive priority

Defenders should prioritize verifying their inventory of CKAN MCP Server instances and upgrading to version 0.4.112 or later to mitigate this vulnerability.

Recommended defensive actions

• Verify inventory of CKAN MCP Server instances
• Upgrade to version 0.4.112 or later
• Review server_url parameter validation
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and references to the fix and affected versions. The vulnerability allows for spoofed responses, potentially impacting data integrity. Defenders should verify server_url parameter validation and prioritize upgrading to version 0.4.112 or later. The official CVE Program record and NIST NVD detail page offer source-provided CVE metadata and vulnerability assessments.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.