CVE-2026-6267
GitLab vulnerability
- Published29 Jul 2026
Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-6267 being actively exploited?
CVE-2026-6267 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.61%.
How severe is CVE-2026-6267?
CVE-2026-6267 has a CVSS 3.1 base score of 8.5, rated high. EPSS estimates a 0.61% probability of exploitation.
Which products are affected by CVE-2026-6267?
Affected products include GitLab.
How do I fix CVE-2026-6267?
Upgrade affected software to a fixed version, for example GitLab 19.0.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-6267 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.