High · published October 29, 2025
⚡ An authenticated attacker could hijack your project runners with just the right permissions – a surprisingly simple breach that affects several GitLab versions! Think of it like a chef at a restaurant sneaking into another kitchen and using their equipment without permission – it’s not just rude, it can mess up the whole meal! If an attacker successfully hijacks project runners, they could execute malicious tasks across different projects, potentially leading to data theft or service disruptions. It’s a serious risk that could compromise your entire development workflow and sensitive information.
Think of it like a chef at a restaurant sneaking into another kitchen and using their equipment without permission – it’s not just rude, it can mess up the whole meal! This vulnerability allows authenticated users with specific permissions to take control of project runners across various GitLab projects, making it easier for them to run unauthorized code.
If an attacker successfully hijacks project runners, they could execute malicious tasks across different projects, potentially leading to data theft or service disruptions. It’s a serious risk that could compromise your entire development workflow and sensitive information. To mitigate this risk, update to GitLab versions 18.3.5, 18.4.3, or 18.5.1 as soon as possible. Review project permissions to ensure appropriate access controls are in place. Regularly monitor logs for any unauthorized access attempts. You've got this! By following these steps, you'll bolster your defenses and keep your projects secure. 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| gitlab/gitlab | ≥ 17.1.0, < 18.3.5 | 18.3.5 |
| gitlab/gitlab | ≥ 18.4.0, < 18.4.3 | 18.4.3 |
| gitlab/gitlab | all versions | — |