Executive Summary
In September 2026, Aikido Security researchers discovered that GitLab's incoming email addresses contain non-expiring access tokens that grant broad privileges across an organization's public and private projects. These automatically assigned email addresses, designed for creating issues via email, can be weaponized by attackers who obtain them to push malicious code, bypass IP restrictions, and execute CI/CD jobs without direct account access. The vulnerability affects the entire GitLab ecosystem, with researchers finding exposed addresses for popular open-source projects during a brief internet scan.
This incident highlights the growing sophistication of supply chain attacks targeting developer platforms and the hidden security implications of seemingly benign productivity features. As organizations increasingly rely on DevOps platforms for critical infrastructure, attackers are exploiting overlooked authentication mechanisms to compromise software supply chains at scale.
Why This Matters Now
Supply chain attacks via developer platforms are surging in 2026, with threat actors exploiting hidden authentication tokens in productivity features to bypass traditional security controls and inject malicious code directly into software repositories.
Attack Path Analysis
Attackers exploited exposed GitLab incoming email addresses containing non-expiring tokens to gain unauthorized access to private repositories, escalated privileges by manipulating project paths and bypassing IP restrictions, moved laterally across multiple projects using the same token, established persistent access through merge requests and CI/CD manipulation, exfiltrated sensitive code and credentials from private repositories, and potentially compromised the entire software supply chain by injecting malicious code into production systems.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers discovered exposed GitLab incoming email addresses containing glimt- tokens through public repositories, documentation, or support files, gaining unauthorized access to GitLab projects without credential compromise
MITRE ATT&CK® Techniques
Valid Accounts: Cloud Accounts
Phishing: Spearphishing Attachment
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Access Token Manipulation
Impair Defenses: Disable or Modify Cloud Firewall
Trusted Relationship
Server Software Component: Web Shell
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Access Control Systems
Control ID: 7.2.1
NYDFS 23 NYCRR 500 – Multi-Factor Authentication
Control ID: 500.12
DORA – Testing of ICT Tools and Systems
Control ID: Article 8
CISA ZTMM 2.0 – Software platforms and applications within the organization are inventoried
Control ID: ID.AM-2
NIS2 Directive – Risk Analysis and Information System Security Policies
Control ID: Article 21.2(a)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
GitLab supply chain attacks targeting DevOps platforms enable code injection, CI/CD compromise, and unauthorized access to private repositories through weaponized email tokens.
Information Technology/IT
IT organizations face elevated supply chain risks from GitLab token abuse, enabling attackers to bypass IP restrictions and execute unauthorized deployments across environments.
Financial Services
Financial institutions using GitLab for application development exposed to supply chain attacks that could compromise sensitive code repositories and regulatory compliance frameworks.
Defense/Space
Defense contractors face critical supply chain vulnerabilities through GitLab email token exploitation, potentially exposing classified codebases and compromising national security applications.
Sources
- GitLab Email Addresses Can Be Weaponized for Supply Chain Attackshttps://www.darkreading.com/application-security/gitlab-email-addresses-supply-chain-attacksVerified
- Aikido Security Research on GitLab Incoming Email Securityhttps://aikido.dev/blog/gitlab-incoming-email-tokensVerified
- GitLab Security Documentation - Incoming Emailhttps://docs.gitlab.com/ee/administration/incoming_email.htmlVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely have constrained the GitLab token exploitation by segmenting repository access and limiting lateral movement across projects. The fabric's identity-aware controls could have reduced the blast radius from exposed email tokens.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Identity-aware access controls would likely have constrained the scope of repository access even when tokens were exposed, limiting which projects could be reached through compromised email addresses.
Control: Zero Trust Segmentation
Mitigation: Microsegmentation policies would likely have prevented path manipulation attacks by enforcing strict project-to-project access boundaries, constraining privilege escalation across repository namespaces even with valid tokens.
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely have blocked cross-project enumeration attempts, constraining lateral access patterns between GitLab repositories and reducing the attack surface for project ID guessing.
Control: Multicloud Visibility & Control
Mitigation: Centralized visibility controls would likely have detected anomalous merge request patterns and CI/CD trigger behaviors, constraining persistent access through automated pipeline manipulation and covert channels.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement would likely have constrained bulk data extraction through merge requests, limiting the volume and frequency of repository content that could be exfiltrated via email-based mechanisms.
While segmentation would likely limit supply chain compromise to specific project boundaries, any successful code injection could still affect downstream applications consuming those particular repositories within the constrained scope.
Impact at a Glance
Affected Business Functions
- Software Development
- DevOps CI/CD Pipeline
- Source Code Management
- Project Management
Estimated downtime: N/A
Estimated loss: N/A
Potential exposure of private source code repositories, proprietary software projects, intellectual property, and development secrets through unauthorized access to GitLab projects via compromised incoming email tokens
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce least privilege access and prevent unauthorized cross-project token reuse through identity-based policy controls
- • Deploy Egress Security & Policy Enforcement to monitor and control outbound communications from development environments, blocking unauthorized data exfiltration attempts
- • Establish Multicloud Visibility & Control to detect anomalous interactions and suspicious automation patterns across GitLab and integrated development platforms
- • Enable Threat Detection & Anomaly Response capabilities to baseline normal development workflows and alert on covert email-based access patterns
- • Rotate all GitLab incoming email tokens organization-wide and scan repositories for exposed addresses as part of comprehensive secrets management practices
