🛡️ CVE-2026-5377 — gitlab

🟡 CVSS 5.0 — Medium ✅ No Known Exploit CWE-863 OSV
5.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Incorrect Authorization in GitLab

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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

CVE-2026-5377 is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

CVE-2026-5377 is recorded against 1 package.

  • gitlab

Timeline and source

Published on 24 April 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

about.gitlab.com (Web)
gitlab.com (Web)
hackerone.com (Web)
nvd.nist.gov (Web)

Details

Severity MEDIUM
CVSS Score 5.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CWE CWE-863
Public Exploit ✅ No
Source OSV
Published 2026-04-24
Updated 2026-08-12
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
gitlab

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in gitlab

CVE-2026-5377 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.