Notifications
Clear all
Topic starter
18/08/2026 2:16 pm
TL;DR: CVE-2026-72766 in n8n can turn an exposed Send Email node into local file disclosure and server-side request forgery when unauthenticated webhooks, SMTP credentials, and untrusted body fields align, according to CYCOGNITO. The core issue is not just patching a type confusion bug, but eliminating workflow conditions that let automation platforms become credential-rich attack surfaces.
NHIMG editorial — based on content published by CYCOGNITO: Sample of assets impacted by n8n Node File Read vulnerability, identified by the CyCognito Platform
By the numbers:
- The affected n8n versions include releases before 1.123.67, 2.31.5, and 2.32.1.
- When public AWS credentials are exposed, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: What fails when an automation workflow can pass untrusted input into a mail node?
A: The failure is trust propagation.
Q: Why do self-hosted workflow platforms create higher secrets risk than ordinary apps?
A: They often sit between multiple systems and store the credentials needed to connect them.
Q: How can security teams know whether n8n-style exposure is actually dangerous?
A: Check three signals together: reachable unauthenticated webhooks, nodes that accept direct external input, and any workflow host that stores reusable credentials.
Practitioner guidance
- Inventory all externally reachable automation instances Identify every self-hosted n8n deployment, including subsidiary, cloud-hosted, and proof-of-concept instances.
- Remove direct untrusted input from email body fields Review every workflow that feeds webhook data into the Send Email node and break the direct expression path where user-controlled values can reach message fields.
- Restrict webhook exposure at the network edge Place reverse proxy or network controls in front of public webhook endpoints so unauthenticated requests cannot reach sensitive workflow paths by default.
What's in the full analysis
CYCOGNITO's full analysis covers the operational detail this post intentionally leaves for the source:
- The exact vulnerable version lines and fix branches for self-hosted n8n deployments
- CyCognito's exposure distribution data across sectors and deployment patterns
- The recommended remediation sequence for webhook control, workflow auditing, and secret rotation
- CyCognito's Emerging Threat Advisory context for CVE-2026-72766
👉 Read CYCOGNITO's analysis of CVE-2026-72766 and n8n file-read exposure →
n8n CVE-2026-72766: what the file-read risk means for teams?
Explore further
18/08/2026 3:09 pm
Workflow automation platforms are becoming concentrated non-human identity assets. n8n instances often store SMTP credentials, environment variables, and integration tokens, which means a flaw in one node can expose an identity-rich control plane rather than a single app. That changes how defenders should classify these systems under IAM and PAM. Treating them as ordinary internal tooling understates the blast radius; practitioners should inventory and govern them as privileged integration services.
A few things that frame the scale:
- When public AWS credentials are exposed, attackers attempt access within an average of 17 minutes, according to LLMjacking: How Attackers Hijack AI Using Compromised NHIs.
- Also from our research: DeepSeek accidentally embedded over 11,000 secrets in its training data and left a database exposed online, revealing more than one million sensitive records including chat histories, backend credentials, and API keys.
A question worth separating out:
Q: Who is accountable when a workflow leaks secrets through deployment abuse?
A: Accountability usually spans repository owners, platform engineering, and the teams that defined the workflow and its permission model. Security governance frameworks expect explicit control ownership, because automation failures are still governance failures. For NHI programmes, the accountable party is whoever owns the machine identity, its scopes, and the approval gates around it.
👉 Read our full editorial: n8n file-read CVE-2026-72766 exposes workflow-hosted secrets
