Skip to main content
VulnerabilityPublished Updated

CVE-2026-73846: ondata ckan-mcp-server · Insufficient Verification of Data Authenticity

Affects ondata ckan-mcp-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.4.112 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.4.112
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade ckan-mcp-server and ondata/ckan-mcp-server to 0.4.112.

Affected software

ProductAffectedFixed in
ondatackan-mcp-serverAffected
  • <0.4.112
Fixed in
  • 0.4.112
GitHubondata/ckan-mcp-serverpkg:github/ondata/ckan-mcp-serverOther threatsAffected
  • <0.4.112
Fixed in
  • 0.4.112

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to version 0.4.112 or later, where the vulnerability is fixed by properly escaping delimiters in request parameter serialization to prevent cache key collisions. Patch status is confirmed by the vendor's versioning information.

Description

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.

References

Community reviews

Loading reviews…