Security vulnerabilities: Gitlab developers advise rapid update

Attackers can exploit several vulnerabilities in Gitlab and, in the worst case, compromise systems.

Unauthorized access conceivable

According to a warning message, two vulnerabilities (CVE-2025-25291, CVE-2025-25292) are considered “critical”. However, systems are only vulnerable if authentication via SAML SSO is active and attackers have already taken over a user account.

The errors can be found in the ruby-saml library that Gitlab uses for this form of login. If the requirements are met, attackers can log in to systems as another user.

The developers state that they have closed the vulnerabilities in Gitlab Community and Enterprise Edition 17.7.7, 17.8.5 and 17.9.2. The secured editions are already running on Gitlab.com. So far, there have been no reports of attackers exploiting the vulnerabilities. Nevertheless, the Gitlab developers recommend installing the patch as soon as possible.

If admins are currently unable to install the security update, they must carry out the workaround listed in the warning message and, among other things, activate two-factor authentication for all accounts.

Further dangers

Attackers can also exploit seven additional vulnerabilities and execute malicious code in the context of the Ruby library graphql (CVE-2025-27407 “high”). However, such attacks are not possible without further ado, and the beta feature Direct Transfer, which is not active by default, must be active.

DoS attacks are also possible and account data can be leaked. The developers have also fixed several bugs in the current versions. Most recently, at the end of February, several security vulnerabilities in Gitlab made the headlines, allowing attackers to execute their commands, among other things.

(des)