CVE-2025-0652: Incorrect Authorization in GitLab

Published Mar 12, 2025
·
Updated

An issue has been discovered in GitLab EE/CE affecting all versions starting from 16.9 before 17.7.7, all versions starting from 17.8 before 17.8.5, all versions starting from 17.9 before 17.9.2 could allow unauthorized users to access confidential information intended for internal use only.

Affected Software

8 affected componentsFixes available
GitLab GitLab EE/CE>=16.9, <17.7.7, >=17.8, <17.8.5, >=17.9, <17.9.2
GitLab GitLab>=16.9.0<17.7.7
GitLab GitLab>=16.9.0<17.7.7
GitLab GitLab>=17.8.0<17.8.5
GitLab GitLab>=17.8.0<17.8.5
GitLab GitLab>=17.9.0<17.9.2
GitLab GitLab>=17.9.0<17.9.2
GitLab GitLab>=16.9<17.7.7, >=17.8<17.8.5, >=17.9<17.9.2
17.7.717.8.517.9.2

Remediation

Information

Upgrade to versions 17.7.7, 17.8.5, 17.9.2.

Event History

Mar 13, 2025
CVE Published
via MITRE·05:55 AM
Data Sourced
via MITRE·05:55 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·06:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 21, 2026
Data Sourced
via GitLab·10:58 PM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-0652?

CVE-2025-0652 is considered a critical vulnerability due to its potential to expose confidential information to unauthorized users.

2

How do I fix CVE-2025-0652?

To fix CVE-2025-0652, upgrade your GitLab EE/CE to version 17.8.5 or later, or to version 17.9.2 or later.

3

What versions are affected by CVE-2025-0652?

CVE-2025-0652 affects GitLab EE/CE versions from 16.9 to 17.7.7, from 17.8 to 17.8.5, and from 17.9 to 17.9.2.

4

What kind of information can be exposed by CVE-2025-0652?

CVE-2025-0652 allows unauthorized users to access confidential information intended for internal users only.

5

Is there a workaround for CVE-2025-0652?

There are no known workarounds for CVE-2025-0652; users must upgrade to a patched version to mitigate the risk.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2025-0652 - Incorrect Authorization in GitLab - SecAlerts