vciy

CVE-2026-21858

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 Unauthenticated File Access via Improper Webhook Request Handling

CVE-2026-218584 of 4 sources documented this
55

rank 55 = 27 + 25 + 1 + 2 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.78447  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 10.0, from the CNA  ·  without this subject the record ranks 30

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-08-28  ·  without this subject the record ranks 54

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 53

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 55

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3.45Mover the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$3.45M = $4.99M incident cost x 0.8814887365328109 exposure x 0.78447 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.78447EPSSNOT IN KEVas of 2026-09-20
Severity10 CRITICALreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.78, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

Palo AltoAtlassianApache Log4j2Ubiquiti IncCisco SecureAdobe Commerce21858

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

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 · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality and integrity loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-20 Improper Input Validationreceipt
Published consequencesCWE-20: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Confidentiality: Read Memory, Read Files or Directories…[email protected]

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.121.0receipt
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.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 5 public repositories, 2026-01-07.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 5 public repositories2026-01-07receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA10 CRITICALreceipt
Exploit probability0.78447 · top 0.44% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes39 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productn8n-io n8nreceipt
Published rangesn8n >= 1.65.0 < 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

Unauthenticated network requestno credentials, no interactionn8n-io n8nCWE-20 improper input validationAdjacent componentsscope changeConfidentiality and integrity lossC:H / I:Hexploits CWE-20scope changedata compromise

What it is stated by the CNA

n8n is an open source workflow automation platform. Versions starting with 1.65.0 and below 1.121.0 enable an attacker to access files on the underlying server through execution of certain form-based workflows. A vulnerable workflow could grant access to an unauthenticated remote attacker, resulting in exposure of sensitive information stored on the system and may enable further compromise depending on deployment configuration and workflow usage. This issue is fixed in version 1.121.0. receipt

NVD's analysis a second authority

weakness
CWE-20
affected versions
n8n >= 1.65.0 < 1.121.0
also scored by
[email protected] 10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

check it yourself github.com cyera.com receipt

Dated events

2026-06-15EPSS moved 0.05 to 0.722026-08-28EPSS moved 0.73 to 0.78

Movement the material steps

8 Jan 20260.0003
15 Jun 20260.72023 · crossed 0.10 and 0.50 · scoring model v2026.06.15
4 Sep 20260.78447

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 34 observations
8 Jan 20260.0003
11 Jan 20260.00025
12 Jan 20260.02697
13 Jan 20260.02955
17 Jan 20260.0513
18 Jan 20260.03721
25 Jan 20260.04303
1 Feb 20260.05371
8 Feb 20260.05817
18 Feb 20260.07694
3 Mar 20260.07058
16 Mar 20260.07425
25 Mar 20260.07692
26 Mar 20260.08494
1 Apr 20260.08732
2 Apr 20260.07614
3 Apr 20260.05754
4 Apr 20260.06625
5 Apr 20260.05754
7 Apr 20260.06625
15 Apr 20260.05754
16 Apr 20260.06625
21 Apr 20260.06439
24 Apr 20260.05754
3 May 20260.06625
9 May 20260.0569
18 May 20260.06939
5 Jun 20260.05899
10 Jun 20260.05117
15 Jun 20260.72023
23 Jun 20260.71647
9 Aug 20260.72549
28 Aug 20260.78197
4 Sep 20260.78447

34 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.78447Published · Public PoC2026-01-07Index as of2026-09-04

Exploit probability more than doubled between 2026-01-11 and 2026-01-12 (0.00025 → 0.02697) and the record had been public for 7 months when this index was last written.

Published 2026-01-07 receipt · Public PoC 2026-01-07 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-3400 · Palo Alto Networks PAN-OSmatches 7 of 9KEV listed · 2024receipt
CVE-2023-22515 · Atlassian Confluence Data Centermatches 7 of 9KEV listed · 2023receipt
CVE-2021-44228 · Apache Log4j2matches 7 of 9KEV listed · 2021receipt
CVE-2026-34910 · Ubiquiti Inc UniFi OS Servermatches 7 of 9KEV listed · 2026receipt
CVE-2025-20393 · Cisco Secure Emailmatches 7 of 9KEV listed · 2025receipt
CVE-2025-54236 · Adobe Commercematches 7 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

13347 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

n8n-io n8n

Of the 4 records in this family that state one, this holds the highest EPSS percentile: 0.99545.

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-2026-21858.

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.