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… (CVE-2026-6267)
A vulnerability in GitLab CE/EE versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling. This issue has been remediated by GitLab in the specified fixed versions.
AI Analysis
Technical Summary
CVE-2026-6267 is a vulnerability in GitLab Community and Enterprise Editions affecting versions from 10.1.0 up to but not including 19.0.5, versions 19.1 up to but not including 19.1.3, and versions 19.2 up to but not including 19.2.1. Under certain conditions, an authenticated user with Developer role could exploit insufficient access controls on internal request handling to gain unauthorized access to information. The vulnerability is classified under CWE-201 (Information Exposure). The CVSS v3.1 base score vector indicates a high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requires low privileges with high attack complexity and no user interaction.
Potential Impact
An attacker with Developer role privileges could access information they are not authorized to see, potentially leading to exposure of sensitive data and compromising confidentiality, integrity, and availability of the system. The impact is rated high based on CVSS metrics.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 19.0.5, 19.1.3, and 19.2.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated beyond applying the official patches.
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… (CVE-2026-6267)
Description
A vulnerability in GitLab CE/EE versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling. This issue has been remediated by GitLab in the specified fixed versions.
CVSS v3.1
Score 8.5high
Affected software
pkg:gem/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-6267 is a vulnerability in GitLab Community and Enterprise Editions affecting versions from 10.1.0 up to but not including 19.0.5, versions 19.1 up to but not including 19.1.3, and versions 19.2 up to but not including 19.2.1. Under certain conditions, an authenticated user with Developer role could exploit insufficient access controls on internal request handling to gain unauthorized access to information. The vulnerability is classified under CWE-201 (Information Exposure). The CVSS v3.1 base score vector indicates a high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requires low privileges with high attack complexity and no user interaction.
Potential Impact
An attacker with Developer role privileges could access information they are not authorized to see, potentially leading to exposure of sensitive data and compromising confidentiality, integrity, and availability of the system. The impact is rated high based on CVSS metrics.
Mitigation Recommendations
GitLab has released official fixes for this vulnerability in versions 19.0.5, 19.1.3, and 19.2.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated beyond applying the official patches.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6fhj-cgmm-xfx6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-6267"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6ae5319c2644c7f89861a4
Added to database: 07/30/2026, 05:46:25 UTC
Last enriched: 07/30/2026, 07:02:01 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.