Back to Feed
VulnerabilitiesSep 24, 2026

Exposed GitLab project email addresses let attackers push code

Exposed GitLab project email addresses allow attackers to push code and access private repositories.

Attackers are exploiting exposed private GitLab email addresses, intended for submitting bug reports, to push code, steal source code, and access secrets in private repositories. These email addresses contain long-lived tokens that act as credentials, and attackers can modify the '-issue' suffix to '-merge-request' to submit merge requests, bypassing IP restrictions. While GitLab has updated its UI and documentation, project maintainers are urged to stop exposing these addresses and reset compromised tokens.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run Aikido?

Get an email when a new story names Aikido, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

GitLab project email addresses, designed for bug report submission, inadvertently contain long-lived authentication tokens that function as credentials — creating a serious access control flaw when exposed publicly. Attackers discovered that simply modifying the '-issue' suffix to '-merge-request' in these addresses allows them to submit merge requests and push code to private repositories, entirely bypassing IP-based restrictions. This matters because long-lived tokens with broad implicit trust effectively become skeleton keys when leaked, enabling source code theft and secrets exposure. The core failure is a combination of poor secret hygiene (publishing email addresses containing tokens) and insufficient token scoping, compounding the risk that no expiration mechanism limits the window of exploitation.

What helps against this

How we list vendors

Entities

GitLab (product)Aikido (vendor)