Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73846)
Summary
Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73846). Data can be tampered with by attackers. Exploitable via canonicalizeParams. Mitigation: upgrade to 0.4.112 or later.
Original description
The description as published by the source.
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, canonicalizeParams in src/utils/cache.ts serializes request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, allowing different logical parameter sets used by buildCacheKey to collide and an attacker to prime a shared cache with a response for a victim's distinct query. This issue is fixed in version 0.4.112.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73846 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like canonicalizeParams over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @aborruso/ckan-mcp-server to 0.4.112 or later.
If unsure, ask your IT team or search "@aborruso/ckan-mcp-server CVE-2026-73846" on the vendor's site.
CVE-2026-73846 (@aborruso/ckan-mcp-server) — CWE-345 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: canonicalizeParams / buildCacheKey / server_url / caches.default
Patched: 0.4.112 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via canonicalizeParams without authentication.
Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: canonicalizeParams / buildCacheKey / server_url / caches.default.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 0.4.112.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@aborruso/ckan-mcp-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@aborruso/ckan-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@aborruso/ckan-mcp-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @aborruso/ckan-mcp-server to 0.4.112ステージング環境で 0.4.112 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com