Leaked n8n API Tokens Exposed Live Instances to Credential Theft
GitGuardian researchers discovered that 321 n8n instances were accepting leaked API tokens in public GitHub commits, exposing a significant security risk. They demonstrated four attack techniques that could be used to access sensitive data and credentials without exploiting any software vulnerabilities. The findings highlight a critical issue due to the prevalence of n8n, a popular low-code automation platform, and the ease with which API tokens can be exposed. The research revealed that a leaked token could grant access to user data, workflow definitions, stored credentials, and execution history, among other sensitive information.
Summary written automatically in our own words from the original article, which belongs to its publisher and remains the reference. It may contain errors. Sources & data
