# CVE-2026-61612: @aborruso/ckan-mcp-server has SSRF via DNS-name → internal IP — incomplete fix of CVE-2026-53509

> Attackers can bypass SSRF guards via DNS resolution to access internal services and cloud metadata, requiring an upgrade to the CKAN MCP Server library.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-798p-78g2-v556

## What is CVE-2026-61612?

CVE-2026-61612 is a medium-severity server-side request forgery vulnerability in ondata ckan-mcp-server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

CKAN MCP Server is a tool for querying CKAN open data portals. Prior to version 0.4.108, the SSRF guard `validateServerUrl` (added for CVE-2026-33060, extended for CVE-2026-53509) validates only the hostname string and never resolves DNS. Any caller-supplied `server_url` whose hostname *resolves* to an internal address passes the guard, so the server issues requests to loopback and cloud metadata (`169.254.169.254`). This is a third bypass of the same guard, and it reaches IMDS — strictly more than CVE-2026-53509, which only reached loopback. Version 0.4.108 contains an updated fix.

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

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

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


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

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

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

## Is CVE-2026-61612 being exploited?

There is no known exploitation of CVE-2026-61612 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61612 is a medium-severity server-side request forgery vulnerability in ondata ckan-mcp-server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61612 in the wild and no public exploit code.

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

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-61612/ (Markdown: https://insights.sbomify.com/CVE-2026-61612/index.md)
```

## Sources

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

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