CVE-2026-85168

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

n8n versions before 1.123.73, 2.35.4, and 2.36.2 contain a remote code execution vulnerability in the Git node. The node reset a fixed list of command-bearing configuration keys before each operation, but that list did not cover the content-filter and merge-driver key families. A repository with local configuration setting one of those keys together with a matching attribute pattern causes git to execute the configured command during an ordinary Add, Commit, Checkout, or Pull operation. The command runs as the n8n process user.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.8% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 3, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
No fix on record yet. Sources: github.
Web page

n8n before 1.123.73 Remote Code Execution via Git Node | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-1.123.73-remote-code-execution-via-git-node
GitHub advisoryMentions a patch (unverified)

Git Node Remote Code Execution via Incomplete Repository-Local Configuration Neutralization · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-mwp5-2m32-r54h

Vendor Advisories for CVE-2026-85168(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 115× 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 152 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 52 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85168?
CVE-2026-85168 is a high-severity vulnerability; its CVE record was published on September 3, 2026. n8n versions before 1.123.73, 2.35.4, and 2.36.2 contain a remote code execution vulnerability in the Git node. The node reset a fixed list of command-bearing configuration keys before each operation, but that list did not cover the content-filter and merge-driver key families. A repository with…
When was CVE-2026-85168 made public?
CVE-2026-85168 was made public on August 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 3, 2026. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-85168 actively exploited?
CVE-2026-85168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85168?
CVE-2026-85168 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-85168?
No fix for CVE-2026-85168 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-85168 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85168

Explore →

Is Your Infrastructure Affected by CVE-2026-85168?

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

Book a Demo →Browse All CVEs