CVE-2025-3396: Incorrect Authorization in GitLab

Published Jul 9, 2025
·
Updated

An issue has been discovered in GitLab EE affecting all versions from 13.3 before 17.11.6, 18.0 before 18.0.4, and 18.1 before 18.1.2 that could have allowed authenticated project owners to bypass group-level forking restrictions by manipulating API requests.

Other sources

GitLab has remediated an issue that could have allowed authenticated project owners to bypass group-level forking restrictions by manipulating API requests.

GitLab

Affected Software

5 affected componentsFixes available
GitLab GitLab EE>=13.3, <17.11.6, >=18.0, <18.0.4, >=18.1, <18.1.2
GitLab GitLab>=13.3.0<17.11.6
GitLab GitLab>=18.0.0<18.0.4
GitLab GitLab>=18.1.0<18.1.2
GitLab GitLab>=13.3<17.11.6, >=18.0<18.0.4, >=18.1<18.1.2
17.11.618.0.418.1.2

Remediation

Information

Upgrade to versions 17.11.6, 18.0.4, 18.1.2 or above.

Event History

Jul 10, 2025
CVE Published
via MITRE·08:31 AM
Data Sourced
via MITRE·08:31 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·08:55 AM
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-3396?

CVE-2025-3396 has been rated as a medium severity vulnerability.

2

How do I fix CVE-2025-3396?

To fix CVE-2025-3396, upgrade GitLab EE to version 17.11.6 or later, or 18.0.4 or later, or 18.1.2 or later.

3

Who is affected by CVE-2025-3396?

CVE-2025-3396 affects all GitLab EE versions from 13.3 before 17.11.6, 18.0 before 18.0.4, and 18.1 before 18.1.2.

4

What are the implications of CVE-2025-3396?

CVE-2025-3396 allows authenticated project owners to bypass group-level forking restrictions, potentially leading to unauthorized access to project resources.

5

Is there a workaround for CVE-2025-3396?

No formal workaround is available for CVE-2025-3396; upgrading to the fixed versions is the recommended solution.

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