SB2025112663 - Multiple vulnerabilities in GitLab CE/EE
Published: November 26, 2025 Updated: November 27, 2025
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 6 secuirty vulnerabilities.
1) Race condition (CVE-ID: CVE-2024-9183)
The vulnerability allows a remote user to escalate privileges within the application.
The vulnerability exists due to a race condition in CI/CD cache implementation. A remote user can obtain credentials from higher-privileged users and perform actions in their context under specific conditions.
2) Input validation error (CVE-ID: CVE-2025-12571)
The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.
The vulnerability exists due to insufficient validation of user-supplied JSON input. A remote attacker can send specially crafted JSON payload to the application and perform a denial of service (DoS) attack.
3) Improper authentication (CVE-ID: CVE-2025-12653)
The vulnerability allows a remote attacker to bypass authentication process.
The vulnerability exists due to an error in account registration feature. A remote non-authenticated attacker can bypass authentication process and join any organization during registration by manipulating certain HTTP headers.
4) Input validation error (CVE-ID: CVE-2025-7449)
The vulnerability allows a remote user to perform a denial of service (DoS) attack.
The vulnerability exists due to insufficient validation of user-supplied input when handling HTTP responses. A remote user can send specially crafted input to the application and perform a denial of service (DoS) attack.
5) Improper authorization (CVE-ID: CVE-2025-6195)
The vulnerability allows a remote user to gain access to sensitive information.
The vulnerability exists due to improper authorization checks in markdown rendering. A remote user can view information from security reports under certain configuration conditions.
6) Information disclosure (CVE-ID: CVE-2025-13611)
The vulnerability allows a remote user to gain access to potentially sensitive information.
The vulnerability exists due to excessive data output in terraform registry. A remote user with access to certain logs to obtain sensitive tokens under specific conditions.
Remediation
Install update from vendor's website.