CVE-2026-53509

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-64173 (ENISA EUVD) · GHSA-g84h-j7jj-x32p (GitHub Security Advisories)Source: ENISA EUVD

5.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CKAN MCP Server is a tool for querying CKAN open data portals. A known vulnerability CVE-2026-33060 indicated tools including ckan_package_search and sparql_query that accept a base_url parameter had the risk of making HTTP requests to arbitrary endpoints without restriction. A fix was applied to filter out ip addresses. However, a method to bypass exists prior to version 0.4.106. CKAN MCP Server validates caller-supplied CKAN server URLs by inspecting only the parsed hostname string before issuing outbound HTTP requests. In src/utils/http.ts, hostname aliases such as ip6-localhost are not equal to localhost, are not dotted IPv4 literals, and are not bracketed IPv6 literals, so they pass the SSRF filter but can resolve to loopback when the server performs the request. A remote MCP caller that can invoke CKAN tools with a server_url can therefore make the server connect to local or private addresses and, for CKAN-shaped responses, receive response-derived data. The updated fix in version 0.4.106 replaced the single hostname === 'localhost' check with a blocked-hostname Set covering ip6-localhost and ip6-loopback.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 7, 2026

Last Modified

October 12, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_release.
GitHub release Patch Available

v0.4.106 - Security fix: SSRF bypass via hostname aliases

Patch available: ondata/ckan-mcp-server v0.4.106

https://github.com/ondata/ckan-mcp-server/releases/tag/v0.4.106
GitHub advisoryMentions a patch (unverified)

SSRF in @aborruso/ckan-mcp-server via base_url allows access to internal networks · CVE-2026-33060 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-3xm7-qw7j-qc8v
GitHub advisoryMentions a patch (unverified)

Potential fix bypass of CVE-2026-33060 · Advisory · ondata/ckan-mcp-server · GitHub

https://github.com/ondata/ckan-mcp-server/security/advisories/GHSA-g84h-j7jj-x32p

Vendor Advisories for CVE-2026-53509(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@aborruso/ckan-mcp-server—
  • every version up to 0.4.106: fixed in 0.4.106
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-27 10:25 UTCOSV refresh
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-25 14:20 UTCEG score recompute
  6. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-18 03:31 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-12 15:57 UTCEG score recompute
  21. 2026-10-11 19:40 UTCEG score recompute
  22. 2026-10-11 16:55 UTCEG score recompute
  23. 2026-10-11 14:19 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 56 more
  1. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-09-28 13:36 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-09-23 06:16 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-09-18 05:50 UTCEG score recompute
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-09-14 07:38 UTCEG score recompute
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-09-13 08:31 UTCEG score recompute
  27. 2026-09-12 03:43 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-09-09 22:57 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  34. 2026-09-05 22:53 UTCEG score recompute
  35. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-08-30 07:42 UTCEG score recompute
  41. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-08-27 21:55 UTCEG score recompute
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-26 12:59 UTCEG score recompute
  47. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-24 20:38 UTCEG score recompute
  49. 2026-08-23 20:50 UTCEG score recompute
  50. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-08-21 22:27 UTCEG score recompute
  52. 2026-08-21 21:54 UTCEG score recompute
  53. 2026-07-30 10:50 UTCEG score recompute
  54. 2026-07-26 12:36 UTCEG score recompute
  55. 2026-07-23 03:19 UTCEG score recompute
  56. 2026-07-07 20:12 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-53509?
CVE-2026-53509 is a medium-severity vulnerability; its CVE record was published on July 7, 2026. CKAN MCP Server is a tool for querying CKAN open data portals. A known vulnerability CVE-2026-33060 indicated tools including ckanpackagesearch and sparqlquery that accept a baseurl parameter had the risk of making HTTP requests to arbitrary endpoints without restriction. A fix was applied to…
When was the CVE record for CVE-2026-53509 published?
The CVE record for CVE-2026-53509 was published on July 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-53509 actively exploited?
CVE-2026-53509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53509?
CVE-2026-53509 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53509?
A fix for CVE-2026-53509 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53509 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53509

Explore →

Is Your Infrastructure Affected by CVE-2026-53509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs