Exposed GitLab Email Addresses Could Let Attackers Create Merge Requests

Summary
Aikido researchers found private GitLab project email addresses exposed in public documentation. Anyone with an address could change its suffix to create merge requests, potentially bypassing IP restrictions; GitLab advises resetting leaked tokens.
Key points
- Aikido researchers found a dozen live GitLab incoming email addresses in public project documentation, including READMEs and support pages.
- The addresses contain long-lived tokens that allow incoming messages to create project issues or tasks as the token owner.
- Changing an address suffix from “-issue” to “-merge-request” can open a merge request; Aikido says the technique also bypasses IP restrictions.
- Potential access depends on the token owner’s permissions. Researchers say an attacker also needs the project path and ID.
- Aikido reported the issue to GitLab in May; GitLab initially closed it as intended behavior, then updated its UI and documentation after a follow-up report.
- GitLab advises keeping these addresses private and resetting the token if exposed. Aikido urges maintainers to remove published addresses and reset affected tokens.
Article Details
- Vulnerability Types
- Exposure of private incoming email addresses containing long-lived project credentials
- Exploitation Status
- reported
- Exploit Availability
- unknown
- Patch Status
- unknown
- Workarounds
- Remove private incoming email addresses from public documentation and reset tokens that were exposed.
