CKAN MCP Server: MQA server allowlist bypass via unanchored regex (isValidMqaServer)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-73845: 0.38% estimated exploitation activity in the next 30 days; percentile 32.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The ckangetmqaquality and ckangetmqaqualitydetails tools restrict their serverurl argument to dati.gov.it via a regular expression. The regex is anchored only at the start and places no boundary after the host, so any URL whose host merely begins with dati.gov.it — or that uses dati.gov.it as URL userinfo before an @ — passes validation while actually targeting an attacker-controlled host. Affected code All of the following return true: | URL | Real host | |-----|-----------| | https://dati.gov.it.attacker.com/x | dati.gov.it.attacker.com (attacker) | | http://dati.gov.it.evil.example/api | dati.gov.it.evil.example (attacker) | | https://dati.gov.it@attacker.com/x | attacker.com (userinfo trick) | After passing this check, serverurl flows into getMqaQuality/getMqaQualityDetails, which call makeCkanRequest(serverUrl, "packageshow", { id }). The server therefore issues a request to the attacker-controlled host and returns its (parsed) response to the caller. Impact - The…

Published by the source

2 Sep 2026, 14:52 UTC

Last modified by the source

2 Sep 2026, 14:52 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-83x6-42hr-jc76

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73845

Advisory: CKAN MCP Server: MQA server allowlist bypass via unanchored regex (`isValidMqaServer`)
IDs: CVE-2026-73845, GHSA-83x6-42hr-jc76
Record: https://patchnext.com/advisories/cve-2026-73845 (revision 1, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @aborruso/ckan-mcp-server 0.4.112. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @aborruso/ckan-mcp-server: affected < 0.4.112; fixed in 0.4.112

## Suggested inspection (read-only)
- `npm ls @aborruso/ckan-mcp-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @aborruso/ckan-mcp-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-83x6-42hr-jc76 (GitHub-reviewed advisory GHSA-83x6-42hr-jc76 lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.112)

Commands are suggestions: review each one before running it.