CVE-2024-1525 Authentication Bypass Using an Alternate Path or Channel in GitLab

Medium 5.3 Published 21 Feb 2024 Updated 11 Oct 2026

An LDAP user can bypass authentication by resetting their password via a secondary email and signing in directly, potentially taking over accounts.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2024-1525?

CVE-2024-1525 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 21 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.1 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 before 16.9.1. Under some specialized conditions, an LDAP user may be able to reset their password using their verified secondary email address and sign-in using direct authentication with the reset password, bypassing LDAP.

Weakness: CWE-288

Which versions are affected by CVE-2024-1525?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `16.1.0`	`16.7.6, 16.8.3, 16.9.1`

Products include Gitlab Gitlab.

How do I fix CVE-2024-1525?

Upgrade gitlab to a fixed version for your release line: 16.7.6, 16.8.3 or 16.9.1.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2024-1525 being exploited?

There is no known exploitation of CVE-2024-1525 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2024-1525, GHSA-2v36-29xm-jp89, UBUNTU-CVE-2024-1525.