CVE-2026-119408

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-30. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-113792 (ENISA EUVD) · GHSA-48fh-2c4x-8wcm (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

n8n before 2.42.6, 2.43.x before 2.43.3, and 3.x before 3.0.1 contains a remote code execution vulnerability via deprecated Function, Function Item, and LangChain Code nodes running outside task runner isolation. Authenticated users who can create, modify, or import workflows naming these hidden node types can execute JavaScript in the n8n main process.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: 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
50th
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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (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.

The score's inputs: 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

October 30, 2026

Last Modified

November 5, 2026

Advisory Details (8)

Auto-updated Oct 30, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

n8n before 2.42.6, 2.43.3 and 3.0.1 Code Execution Outside Task Runner Isolation via Deprecated Function Nodes | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-2.42.6-2.43.3-and-3.0.1-code-execution-outside-task-runner-isolation-via-deprecated-function-nodes
Web page

GitHub - n8n-io/n8n: Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations. · GitHub

https://github.com/n8n-io/n8n
GitHub release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected] (pre-release)

https://github.com/n8n-io/n8n/releases/tag/[email protected]
GitHub release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected] (pre-release)

https://github.com/n8n-io/n8n/releases/tag/[email protected]
Web page

n8n/packages/nodes-base/nodes/Function/Function.node.ts at [email protected] · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/blob/[email protected]/packages/nodes-base/nodes/Function/Function.node.ts#L167
GitHub commit

commit ea8417e29ad6 (n8n-io/n8n)

Fix landed in n8n-io/n8n commit ea8417e29ad6 — awaiting tagged release

https://github.com/n8n-io/n8n/commit/ea8417e29ad6f8b981d9a04b17283d5d77f2b5bb
GitHub advisoryMentions a patch (unverified)

Deprecated Code Nodes Allow Code Execution in the n8n Main Process · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-9p7v-45m2-wxgj

Vendor Advisories for CVE-2026-119408(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 8× in last 7d / 21× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-11 03:45 UTCEchelonGraph re-scored
  5. 2026-11-11 03:45 UTCGHSA enrichmentGHSA-48fh-2c4x-8wcm · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-11-05 22:28 UTCEchelonGraph re-scored
  12. 2026-11-05 22:28 UTCGHSA enrichmentGHSA-48fh-2c4x-8wcm · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-05 21:26 UTCEchelonGraph re-scored
  14. 2026-11-05 21:26 UTCGHSA enrichmentGHSA-48fh-2c4x-8wcm · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-11-05 21:23 UTCEchelonGraph re-scored
  16. 2026-11-05 21:23 UTCGHSA enrichmentGHSA-48fh-2c4x-8wcm · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  18. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  19. 2026-11-03 20:14 UTCEchelonGraph re-scored
  20. 2026-11-03 20:14 UTCGHSA enrichmentGHSA-48fh-2c4x-8wcm · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  22. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  23. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  24. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  25. 2026-10-30 12:26 UTCEchelonGraph re-scored
Show 3 more
  1. 2026-10-30 12:02 UTCENISA EUVD ID recordedEUVD-2026-113792 · Source: ENISA EUVD
  2. 2026-10-30 11:35 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  3. 2026-10-30 11:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119408?
CVE-2026-119408 is a high-severity vulnerability; its CVE record was published on October 30, 2026. n8n before 2.42.6, 2.43.x before 2.43.3, and 3.x before 3.0.1 contains a remote code execution vulnerability via deprecated Function, Function Item, and LangChain Code nodes running outside task runner isolation. Authenticated users who can create, modify, or import workflows naming these hidden…
When was CVE-2026-119408 made public?
CVE-2026-119408 was made public on October 28, 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 October 30, 2026. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-119408 actively exploited?
CVE-2026-119408 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119408?
CVE-2026-119408 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119408?
A fix for CVE-2026-119408 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119408 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-119408?

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