Skip to content
NewA calmer, faster ZeroHour

Exposed GitLab project email addresses let attackers push code

BleepingComputerby Bill Toulas ()3 min read4 · 1 read
AI summary · grok-4.7Summaries by Vani AI

Aikido warns published GitLab incoming-email tokens can let outsiders open merge requests and push code as the owner.

Aikido found private GitLab addresses for the "Email work item to this project" feature published in READMEs, contributing guides, and support pages. Each address embeds a long-lived glimt- token, and changing the suffix from issue to merge-request can open a merge request as the token owner without GitLab checking the sender address. Resulting access follows that user's permissions and may include code changes, CI/CD runs, private repositories, and secrets; IP restrictions are also bypassed. GitLab initially closed Aikido's May HackerOne report as intended behavior, then updated its interface and documentation. Exposed tokens should be reset.

Key facts
  • GitLab incoming-email tokens can open issues or merge requests as the owner.
  • Aikido found about a dozen live addresses in public documentation.
  • GitLab does not verify the sender and incoming email bypasses IP limits.
  • GitLab first called it intended behavior, then updated warnings and docs.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

3 min read at bleepingcomputer.com

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. [...]

BleepingComputer

By Bill Toulas · bleepingcomputer.com

Read the full article at BleepingComputer

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.