How severe is GHSA-3xm7-qw7j-qc8v?

GHSA-3xm7-qw7j-qc8v has a CVSS score of 5.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3xm7-qw7j-qc8v?

GHSA-3xm7-qw7j-qc8v affects the following packages: @aborruso/ckan-mcp-server (npm). Ecosystems affected: npm.

How do I fix GHSA-3xm7-qw7j-qc8v?

Update @aborruso/ckan-mcp-server to 0.4.85 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3xm7-qw7j-qc8v is resolved across your whole dependency graph.

How do I detect GHSA-3xm7-qw7j-qc8v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aborruso/ckan-mcp-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3xm7-qw7j-qc8v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3xm7-qw7j-qc8v?

O3 pinpoints whether GHSA-3xm7-qw7j-qc8v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3xm7-qw7j-qc8v actively exploited in the wild?

No public exploit code has been indexed for GHSA-3xm7-qw7j-qc8v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3xm7-qw7j-qc8v?

GHSA-3xm7-qw7j-qc8v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3xm7-qw7j-qc8v?

GHSA-3xm7-qw7j-qc8v is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3xm7-qw7j-qc8v published, and has it been updated?

GHSA-3xm7-qw7j-qc8v was published on March 18, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-3xm7-qw7j-qc8v

MEDIUM

SSRF in @aborruso/ckan-mcp-server via base_url allows access to internal networks

Also known asCVE-2026-33060

Published

Mar 18, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.27%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦@aborruso/ckan-mcp-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The @aborruso/ckan-mcp-server MCP server provides 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.

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.

{"tool": "ckan_package_search", "arguments": {"base_url": "http://canary:8080/ssrf", "query": "test"}}

Result: Canary received 9 HTTP requests. The high request volume confirms no rate limiting or URL validation.

Root Cause

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.

Impact

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.

Recommended Fix

Validate base_url against a configurable allowlist of permitted CKAN portals
Block private IP ranges (RFC 1918, link-local)
Block cloud metadata endpoints (169.254.169.254)
Sanitize SQL input for datastore queries
SPARQL endpoint allowlist

Credit

Discovered by Andrei Boldyrev of Munio Security Research using munio

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@aborruso/ckan-mcp-server`	all versions	0.4.85

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aborruso/ckan-mcp-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @aborruso/ckan-mcp-server to 0.4.85 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3xm7-qw7j-qc8v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3xm7-qw7j-qc8v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3xm7-qw7j-qc8v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The `@aborruso/ckan-mcp-server` MCP server provides 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. ## 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 canar

O3 Security · Impact-Aware SCA

Is GHSA-3xm7-qw7j-qc8v in your dependencies?

O3 detects GHSA-3xm7-qw7j-qc8v across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works