Is CVE-2026-61612 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61612 being exploited in the wild.

How severe is CVE-2026-61612?

Medium severity, with a CVSS score of 5.7, published 21 September 2026.

Which products and versions are affected?

@aborruso/ckan-mcp-server (npm) <= 0.4.107, SEMVER:introduced=0,fixed=0.4.108.

Is there a fix for CVE-2026-61612?

Yes. @aborruso/ckan-mcp-server (npm): upgrade to 0.4.108 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61612 attacked?

It is attacked over the network.

Am I affected by CVE-2026-61612?

Check whether you run @aborruso/ckan-mcp-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61612: @aborruso/ckan-mcp-server SSRF via DNS name resolution

Q: Is there a fix for CVE-2026-61612?

Yes. @aborruso/ckan-mcp-server (npm): upgrade to 0.4.108 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-61612 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-61612?

Check whether you run @aborruso/ckan-mcp-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61612 · Severity: medium · CVSS 5.7 · Published 2026-09-21

@aborruso/ckan-mcp-server is a Node.js package that exposes CKAN data via the Model Context Protocol. A server-side request forgery (SSRF) vulnerability allows attackers to bypass hostname validation by supplying a domain name that resolves to internal IP addresses (including cloud metadata endpoints). In unauthenticated HTTP deployments, remote attackers can request internal services and receive responses including sensitive data such as cloud IAM credentials.

Technologies: @aborruso/ckan-mcp-server (npm). Vendors: npm.

Quick answers

Is CVE-2026-61612 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61612 being exploited in the wild.
How severe is CVE-2026-61612?: Medium severity, with a CVSS score of 5.7, published 21 September 2026.
Which products and versions are affected?: @aborruso/ckan-mcp-server (npm) <= 0.4.107, SEMVER:introduced=0,fixed=0.4.108.
Is there a fix for CVE-2026-61612?: Yes. @aborruso/ckan-mcp-server (npm): upgrade to 0.4.108 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61612 attacked?: It is attacked over the network.
Am I affected by CVE-2026-61612?: Check whether you run @aborruso/ckan-mcp-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@aborruso/ckan-mcp-server (npm): upgrade to 0.4.108 or later
```
npm install @aborruso/ckan-mcp-server@0.4.108
```

Technical details

The SSRF guard `validateServerUrl` performs only hostname string validation and does not perform DNS resolution, allowing an attacker to supply a hostname that resolves to internal, private, or cloud-reserved addresses (10.x.x.x, 127.x.x.x, 169.254.169.254). The vulnerability exists in `src/utils/http.ts` and affects all tools that accept a `server_url` parameter. The attack vector is network-based and unauthenticated in default HTTP deployments. An attacker can retrieve non-blind responses from internal services, including IMDS metadata endpoints. This is the third bypass of the same guard, with prior fixes (CVE-2026-33060, CVE-2026-53509) addressing only string literals and failing to implement DNS resolution. No official patch has been released.

Affected products

aborruso @ckan-mcp-server all versions through 0.4.107

Identifiers

CVE-2026-61612
GHSA-798p-78g2-v556

Timeline

2026-09-22: disclosed: GHSA-798p-78g2-v556 published; identified as incomplete fix of CVE-2026-53509
2026-09-22: other: No patch available as of advisory date

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.