Skip to content
major vulnerability· requires attention

GitLab is widely used for source control and CI; info disclosure across many versions risks exposing source, secrets and project data, impacting many orgs.

Applications

CVE-2026-6267

8.5
High
EPSS 0.42%Patch availableJul 30, 2026

Authenticated Developer can access unauthorized data in GitLab via access-control flaw

common questions

Is CVE-2026-6267 being exploited?

Not confirmed. CVE-2026-6267 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-6267?

CVE-2026-6267 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-6267?

Yes. A fix has been recorded for CVE-2026-6267. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-6267 affect?

CVE-2026-6267 affects GitLab CE/EE versions 10.1.0 before 19.0.5, GitLab CE/EE 19.1 before 19.1.3, GitLab CE/EE 19.2 before 19.2.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-6267?

Upgrade GitLab to fixed versions (>=19.0.5, >=19.1.3, >=19.2.1)

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitLab CE/EE versions 10.1.0 before 19.0.5GitLab CE/EE 19.1 before 19.1.3GitLab CE/EE 19.2 before 19.2.1
impact

An authenticated Developer can read unauthorized internal information (source code, CI secrets, project data) by abusing insufficient access controls on internal requests.

action required

Patch when possible

affected versions
GitLab GitLab
  • affected>= 10.1.0 and < 19.0.5
  • affected>= 19.1 and < 19.1.3
  • affected>= 19.2 and < 19.2.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free