Key Takeaways
- Attackers exploited a Metabase flaw to access n8n’s analytics data, exposing 136 records and 5 hashed passwords.
- Non-deterministic queries made exact attribution impossible, blurring which users were affected.
- With CISA listing both tools, the incident underscores the need to harden every auxiliary service in your automation supply chain.
Table of Contents
136 Records, 5 Hashes, and the Automation Supply Chain’s Blind Spot
On August 3, 2026, an unauthorized third party exploited a vulnerability in Metabase — the open-source analytics tool used internally by automation platform n8n — and queried data through n8n’s analytics environment.
Three days later, on August 6, n8n’s security team was alerted to the intrusion.
By August 8, the company published its findings: 136 records containing names and email addresses were accessed across both self-hosted and n8n Cloud users.
Five of those records exposed bcrypt-hashed passwords belonging to cloud accounts.
A separate, previously patched bug had once caused a small number of cloud passwords to be stored in plaintext — and 25 account holders were contacted directly as a precaution, though the company considers it unlikely those records were swept up in the breach.
The Non-Deterministic Query Problem That Made Attribution Impossible
Metabase has since patched the vulnerability, terminated active sessions, and revoked the credentials used during the incident.
But one technical detail complicates the forensic picture: the queries the attacker ran returned non-deterministic row sets each time they executed.
That means n8n cannot pinpoint which specific 136 records were accessed from its larger dataset.
Every name-and-email pair in the queried environment exists inside a statistical blur — known to be exposed in aggregate, but individually unconfirmable.
The five bcrypt-hashed password records sit inside that same uncertainty envelope.
Bcrypt remains computationally expensive to crack, which raises the practical barrier significantly.
Still, the hashes are out there, and n8n has rotated potentially affected credentials and notified its Data Protection Officer alongside the Berlin Commissioner for Data Protection and Freedom of Information.
The historical plaintext bug — already fixed prior to this incident — adds a second layer of precautionary response.
Those 25 users were told to reset passwords immediately, even though no evidence places their records inside the exfiltrated set.
For everyone else, n8n’s guidance, as detailed in their official incident update, is straightforward: no direct email means no mandatory action, but resetting your cloud password remains an available precaution.
When CISA Flags Both Your Analytics and Your Automation Stack
The incident lands against a backdrop that makes it harder to dismiss as an isolated third-party failure.
The CISA Vulnerability Summary for the week of July 13, 2026, lists both Metabase and n8n in the same bulletin.
Metabase appears as an open-source business intelligence and embedded analytics tool — the bulletin’s available summary does not confirm the specific Metabase vulnerability exploited here, and additional entries may exist in the full report that were not accessible for review.
Separately, CISA flags n8n versions prior to 2.19.3 for a file path restriction bypass in a legacy component — a distinct weakness from the Metabase vector, but one that compounds the broader security narrative.
For automation professionals, the intersection is the story.
An automation platform depends on a third-party analytics layer.
That analytics layer gets compromised.
Meanwhile, the automation platform itself appears in a federal vulnerability bulletin for an unrelated flaw within the same monthly window.
This is not a single-point failure — it is a supply chain pattern that automation architects see across every stack they manage.
One compromised tool becomes a readout mechanism for data generated by another, and the lines between ‘our code’ and ‘their dashboard’ dissolve the moment an attacker finds the weakest link in the chain.
The fact that n8n’s own Metabase instance was queryable by an unauthorized third party underscores how analytics surfaces — often treated as read-only conveniences — can become high-yield extraction points when not hardened to the same standard as production infrastructure.
Securing the Tools That Watch Your Workflows
The n8n incident does not reveal a flaw in workflow execution engines or automation logic itself — but it exposes the reality that every auxiliary service plugged into an automation ecosystem inherits its trust boundary.
For teams running production automation where third-party analytics dashboards sit adjacent to customer data, the takeaway is not to audit Metabase specifically — it is to audit every tool that can query what your workflows produce. For automation pipelines where that audit gap feels uncomfortably wide, Andres SEO Expert’s approach to secure programmatic SEO and AI automation architecture is designed to close it — explore the service here or start a conversation directly.
Frequently Asked Questions
What was the n8n security incident in August 2026?
On August 3, 2026, an unauthorized third party exploited a Metabase vulnerability to query data through n8n’s analytics environment. n8n was alerted on August 6 and published findings on August 8, revealing that 136 records containing names and email addresses were accessed, including five bcrypt-hashed passwords.
Why can’t n8n identify exactly which records were accessed?
The attacker’s queries returned non-deterministic row sets each time they executed, meaning the specific records varied with every query. As a result, n8n cannot pinpoint which 136 records were accessed from its larger dataset, even though it knows the aggregate set was exposed.
What should n8n users do if they were affected?
n8n’s official guidance states that if you did not receive a direct email, no mandatory action is required, but resetting your cloud password remains a precaution. The 25 users potentially affected by an earlier plaintext password bug were told to reset immediately, and potentially affected credentials have already been rotated.
What is the relationship between Metabase and n8n in this incident?
n8n uses Metabase as an internal analytics tool. The attacker exploited a Metabase vulnerability to query data from n8n’s analytics environment, demonstrating how a third-party analytics layer can become a high-yield extraction point within an automation supply chain.
What did CISA’s vulnerability bulletin flag about n8n and Metabase?
CISA’s weekly vulnerability summary listed both Metabase and n8n. Metabase is flagged as an open-source business intelligence and embedded analytics tool, while n8n versions prior to 2.19.3 are flagged for a file path restriction bypass in a legacy component. These are separate vulnerabilities but appear in the same bulletin, compounding the security narrative.
How can automation teams secure their analytics tools?
The takeaway is to audit every tool that can query what your workflows produce, not just Metabase. Analytics surfaces should be hardened to the same standard as production infrastructure, because every auxiliary service plugged into an automation ecosystem inherits its trust boundary.
