CVE-2026-33060 is a medium-severity (CVSS 5.3) Server-Side Request Forgery (SSRF) vulnerability in @aborruso/ckan-mcp-server. A fix is available for @aborruso/ckan-mcp-server — see the affected versions and patch details below.
CKAN MCP Server: SSRF via base_url allows access to internal networks
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33060.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@aborruso/ckan-mcp-servernpmDescription
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
- Validate
base_urlagainst a configurable allowlist of permitted CKAN portals - Block private IP ranges (RFC 1918, link-local)
- Block cloud metadata endpoints (169.254.169.254)
- Sanitize SQL input for datastore queries
- SPARQL endpoint allowlist
Credit
Discovered by Andrei Boldyrev of Munio Security Research using munio
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @aborruso/ckan-mcp-server | all versions | 0.4.85npm install @aborruso/ckan-mcp-server@0.4.85 |
Affected Products
ckan mcp serverondataDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aborruso/ckan-mcp-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @aborruso/ckan-mcp-server to 0.4.85 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33060 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2026-33060 in your dependencies?
Find it across npm, including transitive dependencies.