CVE-2026-9807: Incorrect Authorization in GitLab

Published May 28, 2026
·
Updated

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed a blocked Project Access Token to continue accessing private resources due to incorrect authorization enforcement.

Affected Software

7 affected components
GitLab GitLab CE/EE>=18.9<18.10.7, >=18.11<18.11.4, >=19.0<19.0.1
GitLab GitLab>=18.9.0<18.10.7
GitLab GitLab>=18.9.0<18.10.7
GitLab GitLab>=18.11.0<18.11.4
GitLab GitLab>=18.11.0<18.11.4
GitLab GitLab=19.0.0
GitLab GitLab=19.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.10.7
  2. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.11.4
  3. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.0.1

Event History

May 28, 2026
CVE Published
via MITRE·07:34 AM
Data Sourced
via MITRE·07:34 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeaknessAffected Software
Apr 28, 58520
Event
via FIRST·03:19 AM
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-9807?

CVE-2026-9807 has a medium severity rating of 4.3.

2

How do I fix CVE-2026-9807?

To remediate CVE-2026-9807, upgrade to GitLab versions 18.10.7, 18.11.4, 19.0.1 or above.

3

What software does CVE-2026-9807 affect?

CVE-2026-9807 affects GitLab CE/EE versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1.

4

What is the nature of the vulnerability in CVE-2026-9807?

CVE-2026-9807 involves incorrect authorization that could allow blocked Project Access Tokens to access private resources.

5

When was CVE-2026-9807 published?

CVE-2026-9807 was published on May 28, 2026.

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