CVE-2026-3607: Access Control Check Implemented After Asset is Accessed in GitLab

Published May 14, 2026
·
Updated

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to bypass package protection rules due to improper access control.

Affected Software

8 affected components
GitLab GitLab CE>=18.3<18.9.7, >=18.10<18.10.6, >=18.11<18.11.3
GitLab GitLab EE>=18.3<18.9.7, >=18.10<18.10.6, >=18.11<18.11.3
GitLab GitLab>=18.3.0<18.9.7
GitLab GitLab>=18.3.0<18.9.7
GitLab GitLab>=18.10.0<18.10.6
GitLab GitLab>=18.10.0<18.10.6
GitLab GitLab>=18.11.0<18.11.3
GitLab GitLab>=18.11.0<18.11.3

Remediation

Information

Upgrade to versions 18.9.7, 18.10.6, 18.11.3 or above.

Event History

May 14, 2026
CVE Published
via MITRE·05:35 AM
Data Sourced
via MITRE·05:35 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeaknessAffected 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-2026-3607?

CVE-2026-3607 has a medium severity level due to potential access control vulnerabilities.

2

How do I fix CVE-2026-3607?

To mitigate CVE-2026-3607, upgrade your GitLab CE or EE versions to 18.9.7, 18.10.6, or 18.11.3 or later.

3

Who is affected by CVE-2026-3607?

CVE-2026-3607 affects users of GitLab CE and EE from version 18.3 up to but not including 18.9.7, 18.10 up to but not including 18.10.6, and 18.11 up to but not including 18.11.3.

4

What does CVE-2026-3607 exploit?

CVE-2026-3607 exploits an access control check which is implemented after an asset has already been accessed, allowing potential privilege escalation.

5

Is there a workaround for CVE-2026-3607?

There is no official workaround for CVE-2026-3607; updating to a patched version is the recommended solution.

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