# CVE-2026-33060: CKAN MCP Server: SSRF via base_url allows access to internal networks

> Attackers can exploit SSRF in CKAN MCP Server to access internal networks and steal cloud metadata credentials via prompt injection.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-3xm7-qw7j-qc8v

## What is CVE-2026-33060?

CVE-2026-33060 is a medium-severity server-side request forgery vulnerability in ondata ckan-mcp-server, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CKAN MCP Server is a tool for querying CKAN open data portals. Versions prior to 0.4.85 provide 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. There is 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. An attack can lead to 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. This issue has been fixed in version 0.4.85.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-33060?

2 open source packages ship an affected version, including @aborruso/ckan-mcp-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@aborruso/ckan-mcp-server` | npm | All versions | 0.4.85 |
| `@aborruso/ckan-mcp-server` | npm | All versions | 0.4.85 |

Products: Ondata Ckan Mcp Server.

## How do I fix CVE-2026-33060?

Upgrade @aborruso/ckan-mcp-server to 0.4.85 or later.

## Is CVE-2026-33060 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33060 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33060 and fix it if it is affected.

What it is: CVE-2026-33060 is a medium-severity server-side request forgery vulnerability in ondata ckan-mcp-server, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33060 exists.

Affected packages and fixed versions:
- @aborruso/ckan-mcp-server (npm): affected all versions; fixed in 0.4.85
- @aborruso/ckan-mcp-server (npm): affected all versions; fixed in 0.4.85

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33060/ (Markdown: https://insights.sbomify.com/CVE-2026-33060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33060
- OSV: https://osv.dev/vulnerability/CVE-2026-33060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33060/
Summaries are generated and may contain mistakes; the official description above is the record.