CKAN MCP Server 0.4.108 Addresses an SSRF Validation Bypass
Tech GuruQuick Answer
CKAN MCP Server through 0.4.107 checks hostname strings without validating their resolved addresses. An attacker-controlled hostname can therefore reach internal services and return their responses. The project's patched-version field lists 0.4.108. Exposure is greatest on unauthenticated self-hosted HTTP deployments; the official Cloudflare Worker cannot reach the internal destinations described in the advisory.
Confirm Scope And Apply The Supported Fix
What to do now: Identify self-hosted HTTP and stdio deployments, update to 0.4.108, and restrict allowed CKAN destinations. Review network access from the MCP process, especially access to internal services and cloud metadata.
Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | @aborruso/ckan-mcp-server through 0.4.107, especially unauthenticated self-hosted HTTP transport deployments |
|---|---|
| Advisory | GHSA-798p-78g2-v556 |
| CVE | CVE-2026-61612 |
| Project advisory publication | 2026-06-22 18:07:01 UTC |
| Recorded source timestamp (historical snapshot) | 2026-09-22 14:51:26 UTC |
| Affected versions | @aborruso/ckan-mcp-server versions through 0.4.107; the official Cloudflare Worker endpoint is sandboxed from the internal destinations described by the project. |
| Fixed version | @aborruso/ckan-mcp-server 0.4.108 |
| CVSS base score | 5.7 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The earlier fix for CVE-2026-53509 blocked selected literal addresses and aliases, not DNS names resolving to private or special addresses. In default stdio use, the advisory describes prompt injection steering a tool argument; unauthenticated HTTP clients can supply it directly. Internal response bodies may be returned to the caller, so this is not only a blind request.
What To Validate Now
- Inventory. Record the npm version, transport, listening interface, authentication boundary, allowed domains and network destinations reachable by the MCP process.
- Establish applicability. Compare each deployment with the authority's affected-version statement: @aborruso/ckan-mcp-server versions through 0.4.107; the official Cloudflare Worker endpoint is sandboxed from the internal destinations described by the project. Do not infer applicability from product family or severity alone.
- Remediate. Apply @aborruso/ckan-mcp-server 0.4.108 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. In an isolated environment, verify permitted CKAN queries and rejection of names resolving to disallowed destinations. Review protection against resolution changes between validation and connection; do not probe production metadata or unrelated internal services.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The GHSA's patched-version field lists 0.4.108, but its older narrative still says no patch was available. This notice uses the structured version field, not an independent code audit or DNS-rebinding test. The project also recommends a default-deny domain allowlist, particularly for HTTP deployments.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
