Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

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

Known CVEs

  • CVE-2026-21858 Critical n8n unauthenticated file access via webhook handling (Ni8mare)
    Jan 7, 2026 · fixed in 1.121.0
  • CVE-2025-68613 Critical Known exploited n8n remote code execution via workflow expression injection
    Dec 22, 2025 · no fixed release in the feed

How many people use it

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.

Sources

Compare it with the others on the Technology watch list