CVE-2026-42449

HIGHNVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-28442 (ENISA EUVD)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedder path (N8NDocumentationMCPServer constructor, getN8nApiClient(), and validateInstanceContext()), the synchronous URL validator in SSRFProtection.validateUrlSync() had no IPv6 checks. IPv4-mapped IPv6 addresses such as http://[::ffff:169.254.169.254] bypassed the cloud-metadata, localhost, and private-IP range checks. An attacker able to supply an n8nApiUrl value could cause the server to issue HTTP requests to cloud metadata endpoints, RFC1918 private networks, or localhost services. Response bodies are returned to the caller (non-blind SSRF), and the n8nApiKey is forwarded in the x-n8n-api-key header to the attacker-controlled target. Projects with deployments embedding n8n-mcp as an SDK using N8NDocumentationMCPServer or N8NMCPEngine with user-supplied InstanceContext are affected. The first-party HTTP server deployment was not primarily affected — it has a second async validator (validateWebhookUrl) that catches IPv6 addresses. This issue has been fixed in version 2.47.14. If users are unable to upgrade immediately as a workaround they can validate URLs before passing to the SDK, restrict egress at the network layer, and reject user-controlled n8nApiUrl values.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
10th
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 (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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

May 7, 2026

Last Modified

October 26, 2026

Advisory Details (2)

Auto-updated May 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders · Advisory · czlonkowski/n8n-mcp · GitHub

https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-56c3-vfp2-5qqj
Web page

Merge commit from fork · czlonkowski/n8n-mcp@9639f75 · GitHub

https://github.com/czlonkowski/n8n-mcp/commit/9639f757853149f0cb16663cc8b6b6468f27a25f

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
n8n-mcp—
  • 2.47.4 up to 2.47.14: fixed in 2.47.14
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× 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.

Showing the most recent 100 of 190 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-26 20:28 UTCEG score recompute
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-25 14:29 UTCEG score recompute
  8. 2026-10-24 21:43 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-18 03:41 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-17 14:26 UTCEG score recompute
  19. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-12 16:07 UTCEG score recompute
  25. 2026-10-11 19:49 UTCEG score recompute
Show 75 more
  1. 2026-10-11 17:03 UTCEG score recompute
  2. 2026-10-11 14:29 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-09-30 08:41 UTCOSV refresh
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-11 15:23 UTCOSV refresh
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  35. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  37. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  38. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  39. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-08-23 19:33 UTCEG score recompute
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-17 12:42 UTCEG score recompute
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-16 04:42 UTCEG score recompute
  49. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-14 03:17 UTCEG score recompute
  52. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-12 16:52 UTCEG score recompute
  54. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-11 15:54 UTCEG score recompute
  56. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-11 01:24 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  59. 2026-08-09 14:40 UTCEG score recompute
  60. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-09 02:28 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  63. 2026-08-08 02:11 UTCEG score recompute
  64. 2026-08-07 01:48 UTCEG score recompute
  65. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  66. 2026-08-05 22:13 UTCEG score recompute
  67. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  68. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  69. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  70. 2026-08-03 19:36 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  72. 2026-08-02 04:29 UTCEG score recompute
  73. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  74. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  75. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-42449?
CVE-2026-42449 is a high-severity vulnerability; its CVE record was published on May 7, 2026. n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedder path (N8NDocumentationMCPServer constructor, getN8nApiClient(), and validateInstanceContext()), the synchronous URL validator in…
When was the CVE record for CVE-2026-42449 published?
The CVE record for CVE-2026-42449 was published on May 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-42449 actively exploited?
CVE-2026-42449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42449?
CVE-2026-42449 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-42449?
A fix for CVE-2026-42449 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42449?

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

Book a Demo →Browse All CVEs