Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-76894

Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-76894)

Summary

Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-76894). Risk of unauthorized operations or information disclosure. Exploitable via postMessage. Mitigation: upgrade to 0.4.112 or later.

Original description

The description as published by the source.

Summary

The MCP Apps UI resource (an interactive DataStore table rendered in the host's webview/iframe) communicates with its parent via postMessage. Its inbound message listener performs no event.origin validation, and its outbound messages are sent with target origin '*'. Any window/frame able to reach the document can inject data into the table and interfere with the MCP UI handshake, and the UI's own JSON-RPC messages are broadcast without an origin restriction.

Affected code

src/resources/datastore-table-ui.ts (inline HTML):

window.addEventListener('message', function (event) {
  var msg = event.data;                    // no check of event.origin
  if (!msg || typeof msg !== 'object') return;
  if (msg.id !== undefined && _pending[msg.id]) { ... resolve/reject pending MCP request ... }
  ...
  if (data && (data.fields || data.records)) initTable(data);   // renders attacker-supplied data
});

// outbound:
window.parent.postMessage({ jsonrpc: '2.0', id: id, method: method, params: params || {} }, '*');
mcpNot: window.parent.postMessage({ jsonrpc:'2.0', method:method, params:params||{} }, '*');

There is no allowlist of accepted origins for inbound messages and no fixed target origin for outbound messages.

Impact

  • Content spoofing. A frame that can postMessage to the UI can supply
    arbitrary fields/records, causing the table to render fabricated rows and
    links (e.g. a phishing __link_url) that appear to come from the quer…

Source: GitHub Security Advisories (Global) 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-76894 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like postMessage over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
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-76894" on the vendor's site.

CVE-2026-76894 (@aborruso/ckan-mcp-server) — CWE-345
Attack surface: postMessage / message / event.origin / fields
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.

❓ What is the problem

A vulnerability (CWE-345) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via postMessage.

📍 Affected scope

Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: postMessage / message / event.origin / fields.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.4.112.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @aborruso/ckan-mcp-server to 0.4.112

    ステージング環境で 0.4.112 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @aborruso/ckan-mcp-server
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.112"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details