CVE-2026-86081

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (46th 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-74275 (ENISA EUVD) · GHSA-j535-v25q-vx3q (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Git node clone operation matched an attacker-controlled destination path against the default N8N_BLOCK_FILE_PATTERNS regular expression. The pattern ^(./).git(/.)$ allowed catastrophic backtracking and ran synchronously in the main n8n process. An authenticated workflow editor could therefore freeze the instance with one workflow execution; the affected default is declared in packages/@n8n/config/src/configs/security.config.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
47
EG Risk 47/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

September 8, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 8, 2026
Patch available. Sources: github, github_release.
GitHub release Patch Available

n8n@2.38.2

Patch available: n8n-io/n8n n8n@2.38.2 (pre-release)

https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2
GitHub release Patch Available

n8n@2.37.7

Patch available: n8n-io/n8n n8n@2.37.7

https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7
GitHub release Patch Available

n8n@1.123.76

Patch available: n8n-io/n8n n8n@1.123.76

https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76
GitHub advisoryMentions a patch (unverified)

Regular Expression Denial of Service in the Default Blocked-File-Pattern Match via a Git Node Clone Path · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-j535-v25q-vx3q

Vendor Advisories for CVE-2026-86081(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmn8n @ 1.123.76 (fixes < 1.123.76)—ghsa
npmn8n @ 2.38.2 (fixes >= 2.38.0, < 2.38.2)—ghsa
npmn8n @ 2.37.7 (fixes >= 2.0.0, < 2.37.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
n8n—
  • every version up to 1.123.76: fixed in 1.123.76
  • 2.38.0 up to 2.38.2: fixed in 2.38.2
  • 2.0.0 up to 2.37.7: fixed in 2.37.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 49× 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.

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. 2 repeat rows among the latest 97 are merged into the row they repeat.

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

Frequently asked(5)

What is CVE-2026-86081?
CVE-2026-86081 is a high-severity vulnerability; its CVE record was published on September 8, 2026. n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Git node clone operation matched an attacker-controlled destination path against the default N8N_BLOCK_FILE_PATTERNS regular expression. The pattern ^(./).git(/.)$ allowed catastrophic backtracking and…
When was the CVE record for CVE-2026-86081 published?
The CVE record for CVE-2026-86081 was published on September 8, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-86081 actively exploited?
CVE-2026-86081 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86081?
CVE-2026-86081 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86081?
A fix for CVE-2026-86081 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86081 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-86081

Explore →

Is Your Infrastructure Affected by CVE-2026-86081?

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