Every automated workflow stands on a stack of keys. One WhatsApp Business token, one AI model API key, one database credential, one OAuth to Google Sheets. As long as the flow runs and notifications arrive on time, hardly anyone looks at that side.
What changed throughout 2026: that side is precisely what started to be targeted.
One key that unlocks all keys
Last March, Pillar Security researchers revealed two critical vulnerabilities in n8n: CVE-2026-27577 (CVSS score 9.4) and CVE-2026-27493 (score 9.5). The latter is particularly concerning because its entry point is the Form node, an endpoint that is indeed public from the start. The payload can simply be sent through the Name field in a "Contact Us" form. If chained with the first vulnerability, an attacker could read the N8N_ENCRYPTION_KEY variable, the key used by n8n to encrypt credentials in the database. Once that key is read, the entire cabinet opens: AWS keys, database passwords, OAuth tokens, API keys. All of these have been patched in versions 2.10.1, 2.9.3, and 1.123.22.
Two weeks later, CVE-2026-33663 emerged, with high severity and a score of 8.5. This is not a server takeover, but something much more mundane yet much closer to the daily routine of the team: in the Community Edition, users with a regular member role can call generic HTTP credentials belonging to their instance colleagues, because name-based credential resolution does not check ownership. One shared server, one team, and secrets leak among members. n8n's official advice is not just to upgrade, but also to rotate any HTTP credentials that have ever been stored there.
Why this is a business issue, not just an IT issue
The usage pattern here is quite typical. n8n is installed on a cheap VPS, left open to the internet so that webhooks can come in, and then connected to the most sensitive data the company has: customer WhatsApp numbers, email addresses, order history. Practical, and indeed that is its appeal.
The problem is, since October 2024, all provisions of Law Number 27 of 2022 on Personal Data Protection are fully in effect, including administrative sanctions in the form of fines of up to 2 percent of annual revenue for violation variables. The entity that is considered the data controller under the regulation is not the automation platform, but the company that runs it. If data leaks through the workflow, the explanation "it's a bug from the tool" will not help anyone.
Small habits that prevent big damage
The good news is that most mitigations do not require a security team. Store secrets only in the Credentials store, never inside Code nodes, Set nodes, or in the body of expressions. Once a secret is attached to the body of a workflow, it gets exported, shared with colleagues, and hangs out in backup files.
Treat workflow edit rights as equivalent to shell access to the server. This is not an exaggerated analogy: expressions that can bypass the sandbox indeed end up executing commands on the host. Then, one credential for one purpose, with the smallest possible scope. Read-only tokens for workflows that only read sheets. Key rotations should be scheduled, not waiting for incidents: after major upgrades, after team members resign, after vendor contracts end.
And the most often forgotten: read the logs. Silent automation failures are automations that cannot be held accountable to anyone.
Agents that can act, not just respond
The stakes rise again when workflows turn into AI agents. Agents do not just read data and summarize it. They send, reply, delete, and decide the next steps. Practically, they are machine identities that have authority in your system, with keys entrusted in one place.
Such authority should not be hung on a single magical API key that is used by many. Mature automation is not measured by how much work has been cut down, but by how calm the team is in answering a simple question: if this key falls into the wrong hands today, how far will the damage go.
References:
- The Hacker News – Critical n8n Flaws Allow Remote Code Execution and Exposure of Stored Credentials (March 11, 2026) → thehackernews.com
- GitHub Advisory Database – CVE-2026-33663: n8n Credential Theft via Name-Based Resolution (Community Edition) (March 25, 2026) → github.com/advisories
- JDIH Kemkomdigi – Law Number 27 of 2022 on Personal Data Protection, Article 57 → jdih.komdigi.go.id