CVE-2026-5377: Improper Access Control issue in issue description renderer impacts GitLab CE/EE

Published Apr 22, 2026
·
Updated

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that could have allowed an authenticated user to access titles of confidential or private issues in public projects due to improper access control in the issue description rendering process.

Other sources

GitLab has remediated an issue that could have allowed an authenticated user to access titles of confidential or private issues in public projects due to improper access control in the issue description rendering process.

GitLab

Affected Software

5 affected componentsFixes available
GitLab GitLab CE>=18.11<18.11.1
GitLab GitLab EE>=18.11<18.11.1
GitLab GitLab>=18.11<18.11.1
18.11.1
GitLab GitLab=18.11.0
GitLab GitLab=18.11.0

Remediation

Information

Upgrade to version 18.11.1 or above.

Event History

Apr 22, 2026
CVE Published
via MITRE·04:04 PM
Data Sourced
via MITRE·04:04 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via GitLab·07:50 AM
DescriptionSeverityAffected Software
Feb 13, 58282
Event
via FIRST·03:02 PM
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-5377?

CVE-2026-5377 is classified as a medium severity vulnerability due to improper access control allowing unauthorized access to private issue titles.

2

How do I fix CVE-2026-5377?

To remediate CVE-2026-5377, upgrade GitLab CE/EE to version 18.11.1 or later.

3

What versions of GitLab are affected by CVE-2026-5377?

CVE-2026-5377 affects all GitLab CE/EE versions from 18.11 before 18.11.1.

4

What impact does CVE-2026-5377 have on GitLab projects?

CVE-2026-5377 allows authenticated users to access titles of confidential or private issues within public projects.

5

Is CVE-2026-5377 a zero-day vulnerability?

CVE-2026-5377 is not a zero-day vulnerability, as it has been publicly documented and patched in the release of GitLab 18.11.1.

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