CVE-2025-11247: Authorization Bypass Through User-Controlled Key in GitLab

Published Dec 11, 2025
·
Updated

GitLab has remediated an issue in GitLab EE affecting all versions from 13.2 before 18.4.6, 18.5 before 18.5.4, and 18.6 before 18.6.2 that could have allowed an authenticated user to disclose sensitive information from private projects by executing specifically crafted GraphQL queries.

Other sources

GitLab has remediated an issue that could have allowed a user to disclose sensitive information from private projects by executing specifically crafted GraphQL queries.

GitLab

Affected Software

4 affected componentsFixes available
GitLab GitLab EE>=13.2<18.4.6, >=18.5<18.5.4, >=18.6<18.6.2
18.4.618.5.418.6.2
GitLab GitLab>=13.2.0<18.4.6
GitLab GitLab>=18.5.0<18.5.4
GitLab GitLab>=18.6.0<18.6.2

Remediation

Information

Upgrade to versions 18.4.6, 18.5.4, 18.6.2 or above.

Event History

Dec 11, 2025
CVE Published
via MITRE·04:04 AM
Data Sourced
via MITRE·04:04 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·05:16 AM
DescriptionSeverityWeaknessAffected Software
Apr 21, 2026
Data Sourced
via GitLab·08:17 PM
DescriptionSeverityAffected Software
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-11247?

CVE-2025-11247 has been classified as a significant vulnerability due to its potential to expose sensitive information from private GitLab projects.

2

How do I fix CVE-2025-11247?

To remediate CVE-2025-11247, upgrade to GitLab versions 18.4.6, 18.5.4, or 18.6.2.

3

What type of information can be disclosed by exploiting CVE-2025-11247?

Exploitation of CVE-2025-11247 could allow the disclosure of sensitive information stored in private GitLab projects.

4

Which versions of GitLab are affected by CVE-2025-11247?

CVE-2025-11247 affects GitLab EE versions prior to 18.4.6, 18.5.4, and 18.6.2.

5

Is there a workaround for CVE-2025-11247?

There are no public workarounds for CVE-2025-11247; upgrading to the patched versions is the recommended action.

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