SSRF in @aborruso/ckan-mcp-server via base_url allows access to internal networks
CVE-2026-33060GHSA-3xm7-qw7j-qc8v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@aborruso/ckan-mcp-server 0.4.85), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.4.85
- Fixed in
- 0.4.85
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-3xm7-qw7j-qc8v lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.85 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3xm7-qw7j-qc8v lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.85
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-33060: 0.29% estimated exploitation activity in the next 30 days; percentile 22.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The @aborruso/ckan-mcp-server MCP server provides tools including ckanpackagesearch and sparqlquery that accept a baseurl 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. Result: Canary received 9 HTTP requests. The high request volume confirms no rate limiting or URL validation. Root Cause No URL validation on baseurl parameter. No private IP blocking (RFC 1918, link-local 169.254.x.x), no cloud metadata blocking. The sparqlquery and ckandatastoresearchsql tools also accept arbitrary base URLs and expose injection surfaces. Impact Internal network scanning, cloud metadata…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-3xm7-qw7j-qc8v
- Revision 1 · created ·
Published from osv record GHSA-3xm7-qw7j-qc8v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-33060 Advisory: SSRF in @aborruso/ckan-mcp-server via base_url allows access to internal networks IDs: CVE-2026-33060, GHSA-3xm7-qw7j-qc8v Record: https://patchnext.com/advisories/cve-2026-33060 (revision 2, source checked 26 Oct 2026, 12:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @aborruso/ckan-mcp-server 0.4.85. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @aborruso/ckan-mcp-server: affected < 0.4.85; fixed in 0.4.85 ## Suggested inspection (read-only) - `npm ls @aborruso/ckan-mcp-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @aborruso/ckan-mcp-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-3xm7-qw7j-qc8v (OSV record GHSA-3xm7-qw7j-qc8v lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.85 (fixed)) - Verified: https://github.com/advisories/GHSA-3xm7-qw7j-qc8v (GitHub-reviewed advisory GHSA-3xm7-qw7j-qc8v lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.85) Commands are suggestions: review each one before running it.
Loading voting…