Executive Summary
In August 2026, GitGuardian researchers identified 321 n8n instances accepting API tokens that had been exposed in public GitHub commits. This exposure allowed unauthorized access to sensitive data and downstream credentials without exploiting any software vulnerabilities. The investigation revealed that 36% of the reachable instances tested were vulnerable, highlighting significant security risks associated with leaked API tokens in workflow automation platforms.
This incident underscores the critical importance of securing API tokens and credentials, especially in platforms like n8n that integrate with various internal systems. Organizations must implement robust credential management practices and regularly audit their repositories to prevent unauthorized access and potential data breaches.
Why This Matters Now
The increasing integration of automation platforms like n8n into organizational workflows amplifies the potential impact of credential leaks. As attackers continuously exploit exposed API tokens, it is imperative for organizations to proactively secure their credentials and monitor for unauthorized access to prevent data breaches and maintain operational integrity.
Attack Path Analysis
Attackers exploited leaked n8n API tokens to gain unauthorized access to instances, allowing them to enumerate workflows and credentials. They escalated privileges by creating and executing new workflows, leveraging stored credentials to access connected services. Lateral movement was achieved by pivoting through integrated systems, expanding their foothold. Command and control were established by manipulating workflows to communicate with attacker-controlled endpoints. Data exfiltration occurred as sensitive information and credentials were extracted via these workflows. The impact included unauthorized access to multiple systems, potential data breaches, and compromised automation processes.
Kill Chain Progression
Initial Compromise
Description
Attackers obtained leaked n8n API tokens from public GitHub repositories, granting unauthorized access to n8n instances.
Related CVEs
CVE-2025-68613
CVSS 8.8A critical Remote Code Execution (RCE) vulnerability in n8n's workflow expression evaluation system allows authenticated users to execute arbitrary code with the privileges of the n8n process.
Affected Products:
n8n n8n – 0.211.0 to 1.120.3
Exploit Status:
exploited in the wildCVE-2026-65599
CVSS 6.5n8n versions before 1.123.64 contain a credential exposure vulnerability where the full PEM private key is mistakenly placed in the JWT header's kid field, potentially allowing attackers to impersonate the service account.
Affected Products:
n8n n8n – < 1.123.64
Exploit Status:
no public exploitCVE-2026-42282
CVSS 4.3An information disclosure vulnerability in n8n-mcp exposes credentials in server logs when running in HTTP transport mode, potentially allowing unauthorized access to sensitive information.
Affected Products:
n8n n8n-mcp – < 2.47.13
Exploit Status:
no public exploitCVE-2026-45732
CVSS 8.1An authentication bypass flaw in n8n allows attackers to overwrite OAuth credentials and hijack shared integrations, leading to unauthorized access and potential data exfiltration.
Affected Products:
n8n n8n – < 2.20.0
Exploit Status:
no public exploitCVE-2026-54305
CVSS 9.9n8n's Dynamic Credentials feature lacks proper ownership or scope checks, allowing authenticated users to enumerate and manipulate credentials associated with private workflows.
Affected Products:
n8n n8n – < 1.123.55
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Valid Accounts
Unsecured Credentials: Credentials in Files
Account Discovery: Local Account
Email Collection
Exfiltration Over Web Service: Exfiltration to Cloud Storage
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Secure Software Development
Control ID: 6.4.3
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Identity Governance
Control ID: Pillar 2
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
n8n API token exposure creates critical supply-chain risks for IT automation platforms, enabling credential theft and lateral movement across integrated systems.
Financial Services
Leaked automation tokens expose banking APIs, payment processing credentials, and sensitive financial data through compromised workflow integrations and stored credentials.
Health Care / Life Sciences
Healthcare automation platforms face HIPAA compliance violations through exposed patient data workflows, API credentials, and integrated medical system access paths.
Computer Software/Engineering
Software development workflows expose GitHub tokens, deployment credentials, and source code through compromised n8n instances connecting development tool chains.
Sources
- Leaked n8n API Tokens Exposed Live Instances to Credential Thefthttps://thehackernews.com/2026/08/leaked-n8n-api-tokens-exposed-live.htmlVerified
- n8n before 1.123.64 Credential Exposure via JWT Headerhttps://www.vulncheck.com/advisories/n8n-before-credential-exposure-via-jwt-headerVerified
- CVE-2025-68613 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2025-68613Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it would likely limit unauthorized access and lateral movement within the cloud environment, thereby reducing the attacker's ability to exploit interconnected systems.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The unauthorized access to n8n instances would likely be constrained, limiting the attacker's ability to exploit the compromised API tokens.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges within the n8n environment would likely be limited, reducing the scope of potential damage.
Control: East-West Traffic Security
Mitigation: The attacker's ability to move laterally to other integrated systems would likely be constrained, limiting the expansion of their foothold.
Control: Multicloud Visibility & Control
Mitigation: The establishment of command and control channels to external attacker infrastructure would likely be restricted, reducing the attacker's ability to maintain control.
Control: Egress Security & Policy Enforcement
Mitigation: The exfiltration of sensitive data to external destinations would likely be limited, reducing the risk of data breaches.
The overall impact of the attack would likely be reduced, limiting unauthorized access and potential data breaches.
Impact at a Glance
Affected Business Functions
- Workflow Automation
- Data Integration
- API Management
Estimated downtime: N/A
Estimated loss: N/A
Potential exposure of sensitive credentials and API tokens, leading to unauthorized access to connected services and data.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to restrict access between workloads and minimize lateral movement.
- • Enforce Egress Security & Policy Enforcement to control outbound traffic and prevent unauthorized data exfiltration.
- • Utilize Multicloud Visibility & Control to monitor and manage security policies across cloud environments.
- • Deploy Threat Detection & Anomaly Response mechanisms to identify and respond to suspicious activities promptly.
- • Regularly audit and rotate API tokens and credentials to reduce the risk of unauthorized access due to credential leakage.



