PT-2026-26096 · Npm · @Aborruso/Ckan-Mcp-Server

Published

2026-03-18

·

Updated

2026-03-18

·

CVE-2026-33060

CVSS v3.1

5.3

Medium

AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Summary

The @aborruso/ckan-mcp-server MCP server provides tools including ckan package search and sparql query that accept a base url parameter, making HTTP requests to arbitrary endpoints without restriction. A CKAN portal client has no legitimate reason to contact cloud metadata or internal network services.

Severity

Attack complexity is HIGH because exploitation requires prompt injection via malicious content (webpage, document) while the victim's AI assistant has this MCP server connected.

Proof of Concept

Tested inside Docker-in-Docker isolated environment with canary HTTP sidecar.
{"tool": "ckan package search", "arguments": {"base url": "http://canary:8080/ssrf", "query": "test"}}
Result: Canary received 9 HTTP requests. The high request volume confirms no rate limiting or URL validation.

Root Cause

No URL validation on base url parameter. No private IP blocking (RFC 1918, link-local 169.254.x.x), no cloud metadata blocking. The sparql query and ckan datastore search sql tools also accept arbitrary base URLs and expose injection surfaces.

Impact

Internal network scanning, cloud metadata theft (IAM credentials via IMDS at 169.254.169.254), potential SQL/SPARQL injection via unsanitized query parameters. Attack requires prompt injection to control the base url parameter.

Recommended Fix

  1. Validate base url against a configurable allowlist of permitted CKAN portals
  2. Block private IP ranges (RFC 1918, link-local)
  3. Block cloud metadata endpoints (169.254.169.254)
  4. Sanitize SQL input for datastore queries
  5. SPARQL endpoint allowlist

Credit

Discovered by Andrei Boldyrev of Munio Security Research using munio

Fix

SSRF

Weakness Enumeration

CWE-918

Related Identifiers

CVE-2026-33060
GHSA-3XM7-QW7J-QC8V

Affected Products

@Aborruso/Ckan-Mcp-Server