vciy

CVE-2025-68613

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

n8n Vulnerable to Remote Code Execution via Expression Injection

CVE-2025-686134 of 4 sources documented this
82

rank 82 = 40 + 22 + 8 + 4 + 8

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.99105 · CISA KEV listed  ·  without this subject the record ranks 42

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 60

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-01-14  ·  without this subject the record ranks 74

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 78

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 74

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.95Mover the next 30 days, if this record is yours
Movement+$2.75Mon 2026-01-14, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$4.95M = $4.99M incident cost x 1 exposure x 0.99105 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.99105EPSSKEV · LISTED
Severity10 CRITICALreceipt
Harmtotal lossreceipt
Exploitationin the wild · KEVreceipt
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.99, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
GitHub_M10 CRITICALreceipt
NVD8.8 HIGHreceipt
What it costs
GitHub_MComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
NVDComplete confidentiality, integrity and availability lossreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running n8n-io n8n? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-913 Improper Control of Dynamically-Managed Code Resourcesreceipt
Published consequencesCWE-913: Integrity: Execute Unauthorized Code or Commands; Other, Integrity: Varies by Context, Alter Execution Logic[email protected]
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchn8n 1.120.4receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2026-03-25receipt
CISA required actionApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.receipt
Published to CISA KEV82 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2026-03-11.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 33 public repositories2025-12-22receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2026-03-11receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA10 CRITICALreceipt
CVSS, NVD8.8 HIGHreceipt
Exploit probability0.99105 · top 0.07% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes47 · last 16 Sep 2026derived

Affected & Fixed Versions as published

Affected productn8n-io n8nreceipt
Published rangesn8n >= 0.211.0 < 1.120.4; n8n 1.121.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires low privilegesCISA KEV listingadded 03-11 · due 03-25n8n-io n8nCWE-913 weaknessAdjacent componentsscope changeFull compromise (C/I/A)C:H / I:H / A:Hmandates remediationexploits CWE-913scope changedata compromise

What it is stated by the CNA

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. receipt

Read the rest of the CNA's description

Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-913
affected versions
n8n >= 0.211.0 < 1.120.4; n8n 1.121.0
also scored by
[email protected] 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

The CNA scored it 10 and NVD 8.8. Both are shown because both were published; we do not pick one.

check it yourself github.com github.com github.com github.com receipt

Dated events

2026-01-14EPSS moved 0.08 to 0.632026-03-11Added to CISA KEV2026-03-25CISA remediation due2026-06-15EPSS moved 0.68 to 0.98

Movement the material steps

20 Dec 20250.0022
14 Jan 20260.6349 · crossed 0.10 and 0.50
20 Jan 20260.73859
23 May 20260.63045
15 Jun 20260.98011 · crossed 0.90 · scoring model v2026.06.15
28 Aug 20260.99105
Show all 33 observations
20 Dec 20250.0022
25 Dec 20250.03549
3 Jan 20260.07781
6 Jan 20260.08424
14 Jan 20260.6349
18 Jan 20260.63782
20 Jan 20260.73859
6 Feb 20260.71719
16 Feb 20260.74583
18 Feb 20260.76497
25 Feb 20260.78209
3 Mar 20260.7898
12 Mar 20260.76931
30 Mar 20260.79157
14 Apr 20260.80676
20 Apr 20260.7997
21 Apr 20260.78381
30 Apr 20260.8026
8 May 20260.81678
17 May 20260.71842
18 May 20260.67071
20 May 20260.65759
23 May 20260.63045
24 May 20260.65759
26 May 20260.63045
30 May 20260.65759
5 Jun 20260.63045
8 Jun 20260.70699
9 Jun 20260.68312
15 Jun 20260.98011
23 Jun 20260.97875
16 Aug 20260.9795
28 Aug 20260.99105

33 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.99105Published2025-12-19Public PoC2025-12-22CISA KEV2026-03-11Index as of2026-09-04

Listed by CISA 82 days after it published and the record had been public for 8 months when this index was last written.

Published 2025-12-19 receipt · Public PoC 2025-12-22 receipt · CISA KEV 2026-03-11 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Its defect family

n8n-io n8n

Of the 2 records in this family, this is the only one with public proof-of-concept code, and it holds 33 references to it.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-68613.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.