← Search results
CVE-LINKED INVENTORY23 SECURITY RECORDS
n8n
n8n
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at n8n, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-59259 | 15 Jul 2026 | < 1.123.61; < 2.28.1; < 2.27.4 | 1.123.61; 2.28.1; 2.27.4 | Update reference ↗ |
| CVE-2026-59254 | 15 Jul 2026 | < 2.28.1; < 2.27.4 | 2.28.1; 2.27.4 | Update reference ↗ |
| CVE-2026-56353 | 15 Jul 2026 | < 1.123.22; 2.0.0 < 2.9.3; 2.10.0 < 2.10.1 | 1.123.22; 2.9.3; 2.10.1 | Update reference ↗ |
| CVE-2026-56352 | 15 Jul 2026 | < 2.19.3 | 2.19.3 | Update reference ↗ |
| CVE-2026-56349 | 15 Jul 2026 | < 2.10.0 | 2.10.0 | Update reference ↗ |
| CVE-2026-58661 | 10 Jul 2026 | < 2.28.0; < 1.123.58 | 2.28.0; 1.123.58 | Update reference ↗ |
| CVE-2026-56354 | 10 Jul 2026 | < 1.123.24; 2.0.0-rc.0 < 2.10.4; 2.11.0 < 2.12.0; < 2.10.4 | 1.123.24; 2.10.4; 2.12.0 | Update reference ↗ |
| CVE-2026-59257 | 8 Jul 2026 | < 1.123.61; < 2.28.1; < 2.27.4 | 1.123.61; 2.28.1; 2.27.4 | Update reference ↗ |
| CVE-2026-59253 | 8 Jul 2026 | < 2.28.0 | 2.28.0 | Update reference ↗ |
| CVE-2026-56778 | 8 Jul 2026 | < 2.26.2; < 2.25.7 | 2.26.2; 2.25.7 | Update reference ↗ |
| CVE-2026-56776 | 8 Jul 2026 | < 1.123.55; < 2.26.2; < 2.25.7 | 1.123.55; 2.26.2; 2.25.7 | Update reference ↗ |
| CVE-2026-56775 | 8 Jul 2026 | < 1.123.55; < 2.26.2; < 2.25.7 | 1.123.55; 2.26.2; 2.25.7 | Update reference ↗ |
| CVE-2026-56360 | 8 Jul 2026 | < 1.123.18; 2.0.0 < 2.6.2 | 1.123.18; 2.6.2 | Update reference ↗ |
| CVE-2026-56359 | 8 Jul 2026 | < 2.8.0; < 2.6.4 | 2.8.0; 2.6.4 | Update reference ↗ |
| CVE-2025-71380 | 4 Jul 2026 | n8n: ≤ 1.114.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-56777 | 30 Jun 2026 | < 2.26.2; < 2.25.7 | 2.26.2; 2.25.7 | Update reference ↗ |
| CVE-2026-56356 | 30 Jun 2026 | < 1.123.27; 2.0.0-rc.0 < 2.13.3; 2.14.0 < 2.14.1; < 2.14.1; < 2.13.3 | 1.123.27; 2.13.3; 2.14.1 | Update reference ↗ |
| CVE-2026-56350 | 30 Jun 2026 | < 2.8.0 | 2.8.0 | Update reference ↗ |
| CVE-2026-56358 | 24 Jun 2026 | < 1.123.25; 2.0.0-rc.0 < 2.11.2; < 2.11.2 | 1.123.25; 2.11.2 | Update reference ↗ |
| CVE-2026-56351 | 24 Jun 2026 | < 2.4.0 | 2.4.0 | Update reference ↗ |
| CVE-2026-56357 | 22 Jun 2026 | < 1.123.15; 2.0.0 < 2.5.0 | 1.123.15; 2.5.0 | Update reference ↗ |
| CVE-2026-56348 | 22 Jun 2026 | < 2.20.0 | 2.20.0 | Update reference ↗ |
| CVE-2025-68613 | 19 Dec 2025 | n8n: >= 0.211.0, < 1.120.4, = 1.121.0 | The Cyber Centre recommends that organizations upgrade affected instances of n8n to the latest supported version. The table below shows affected and patched versions for each CVE: Affected product CVE Affected versions Patched versions n8n CVE-2025-68613 version 0.211.0 to versions prior to 1.120.4, 1.121.1 and 1.122.0 1.120.4, 1.121.1, and 1.122.0 n8n CVE-2026-21858 version 1.65.0 to versions prior to 1.121.0 1.121.0 n8n CVE-2026-21877 versions prior to 0.121.2 1.121.3 Note: n8n 1.X version will reach end of life (EOL) by beginning of March 2026 Footnote 9 . If patching is not immediately possible, the vendor suggests that users may restrict or disable publicly accessible webhook and form endpoints until upgrading is complete Footnote 10 . In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre's Top 10 IT Security Actions with an emphasis on the following topics Footnote 11 . Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal , or email contact@cyber.gc.ca . | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.