Is my AI tool safe?Workflow automationn8n
Is n8n safe?
No tool is safe or unsafe on its own: it depends on what it can reach and how it is set up. The record for n8n: 1 incident in this center's library and 2 CVEs in its advisory feed (2 critical), the newest published Jan 7, 2026. Below: what went wrong, what was fixed, and how to use it safely.
What to watch for
The most-starred automation tool on GitHub and a favorite target of autonomous attack agents, which scan for exposed instances and run public exploits against them. Two critical CVEs in the feed.
How to use it safely
Never expose the editor to the internet, patch on the day an advisory lands, and give each workflow its own least-privilege credentials.
What it can reach
- Often exposed to the internet
- Runs commands with your permissions
- Holds API keys and tokens
- Connected to mail, files, chat or CRM
What went wrong: incidents in the library
- An open-source agent and DeepSeek run hundreds of attacks for one operator High
Unit 42 documented a single operator who used the open-source Hermes Agent framework with DeepSeek as its reasoning model to find internet-facing systems, pick public exploits and attack them with little further input. It went…
Known CVEs
- CVE-2026-21858 Critical n8n unauthenticated file access via webhook handling (Ni8mare)
- CVE-2025-68613 Critical Known exploited n8n remote code execution via workflow expression injection
How many people use it
- 205k GitHub stars · GitHub
- 113k npm downloads in a week (Sep 22 to 28, 2026) · npm download counts
A high CVE count can mean heavy scrutiny as much as weak engineering, so read the incidents and advisories, not only the number. The counts are what this center has recorded, not every flaw ever found; usage figures are the vendors' and registries' own published numbers.