
Private GitLab email addresses that allow developers to push issues or tasks to a project are being deliberately exposed in READMEs, contributing guides, and support pages used to collect bug reports.
The addresses are part of a built-in GitLab feature called "Email work item to this project" and contain a long-lived token tied to the developer’s account.
These addresses are generated automatically and contain a string that serves as a credential for creating work items via email. When an external client sends a message to one of them, GitLab parses it into a project issue or task.
Researchers at application security company Aikido found multiple private GitLab addresses exposed in public documentation and are warning about the associated risk.
An attacker could use them to compromise GitLab accounts in attacks that push code to protected branches of private repositories, steal source code, collect secrets from CI/CD variables, or access confidential issues.