Executive Summary
GitGuardian found 4,576 n8n API tokens in public GitHub commits; 321 live instances accepted them, and researchers showed four ways to reach sensitive data and downstream credentials without any software flaw.
What Happened
GitGuardian researchers found 321 n8n instances accepting API tokens exposed in public GitHub commits and demonstrated four ways attackers could use them to access sensitive data and downstream credentials without exploiting a software vulnerability. We scanned public GitHub commits for exposed n8n API tokens and identified 4,576 unique credentials associated with 1,255 hostnames. Of the 896
Affected Products
- n8n
Vulnerability / Attack Technique
Leaked API tokens for workflow automation instances
Technical Mechanism
Valid tokens committed to GitHub give access to n8n instances, which hold credentials for connected services.
AI Security Category
LLM02:2025 Sensitive Information Disclosure
Relevant Frameworks
RealGround Analysis
Automation platforms like n8n often run AI agent workflows and store many service credentials. RealGround analysis: one leaked token can open every connected system.
Recommended Controls
- Rotate n8n API tokens and scan commits for them
- Do not expose n8n instances publicly
- Scope credentials stored in automation platforms
Related RealGround Service
AI Security Readiness Assessment · or start with the free AI Agent Security Scanner.
Sources
thehackernews.com: https://thehackernews.com/2026/08/leaked-n8n-api-tokens-exposed-live.html
Summary and analysis written by RealGround from the source above; last updated 2026-10-18.