An authentication bypass vulnerability in GitLab CE/EE allows attackers to circumvent two-factor authentication, posing a severe risk to account integrity.

This flaw, categorized as an unchecked return value (CWE-252), permits an unauthenticated attacker to bypass two-factor authentication protocols if they possess specific knowledge of a target's credential ID.

The ability to bypass two-factor authentication significantly degrades the security posture of the GitLab instance, potentially allowing unauthorized access to sensitive source code, project management data, and CI/CD pipelines. With a CVSS score of 7.4, this high-severity vulnerability represents a substantial risk of account takeover and potential lateral movement within the development environment.

Immediate Action: Upgrade all instances of GitLab CE/EE to versions 18.6.4, 18.7.2, 18.8.2, or newer to apply the security patch.

Proactive Monitoring: Monitor authentication logs for unusual login patterns or repeated failed attempts followed by successful access using Two-Factor Authentication methods.

Compensating Controls: Ensure that network-level access controls restrict exposure of the GitLab instance to untrusted networks, and consider enforcing strict IP allowlisting for administrative access.

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the linked HackerOne report (3476052).

Given the high CVSS score and the availability of a published proof-of-concept, this vulnerability should be prioritized for immediate remediation. Organizations running the affected versions of GitLab must apply the vendor-provided patches without delay to prevent unauthorized access and protect critical intellectual property stored within the platform.