High · published December 11, 2025
⚡ An unauthenticated user can potentially perform unauthorized actions through a sneaky script injection in the Swagger UI! Think of it like a restaurant where someone can sneak in a fake menu, convincing the staff to serve a dish that wasn’t ordered — that’s the kind of trouble this vulnerability can brew! An attacker could exploit this vulnerability to manipulate the application and act as another user, leading to unauthorized data access or actions. This could result in data leaks, unauthorized changes, or even affecting the integrity of your project. The fallout could be absolutely devastating!
Think of it like a restaurant where someone can sneak in a fake menu, convincing the staff to serve a dish that wasn’t ordered — that’s the kind of trouble this vulnerability can brew! This vulnerability allows unauthenticated users to inject malicious external scripts into the Swagger UI of GitLab, exploiting weaknesses in the application to perform unauthorized actions on behalf of other users.
An attacker could exploit this vulnerability to manipulate the application and act as another user, leading to unauthorized data access or actions. This could result in data leaks, unauthorized changes, or even affecting the integrity of your project. The fallout could be absolutely devastating! To mitigate this risk, patch GitLab to version 18.4.6, 18.5.4, or 18.6.2 immediately. Review your Swagger UI settings to ensure proper security controls are in place. Regularly audit your application for similar vulnerabilities. You've got this! With these steps, you'll have your GitLab environment secured in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| gitlab/gitlab | ≥ 15.11.0, < 18.4.6 | 18.4.6 |
| gitlab/gitlab | ≥ 15.11.0, < 18.4.6 | 18.4.6 |
| gitlab/gitlab | ≥ 18.5.0, < 18.5.4 | 18.5.4 |
| gitlab/gitlab | ≥ 18.5.0, < 18.5.4 | 18.5.4 |
| gitlab/gitlab | ≥ 18.6.0, < 18.6.2 | 18.6.2 |
| gitlab/gitlab | ≥ 18.6.0, < 18.6.2 | 18.6.2 |