# CVE-2026-6267 — GitLab

> As of 2026-07-31, CVE-2026-6267 is a HIGH-severity vulnerability in GitLab, CVSS v3.1 8.5, EPSS 0.3% (26.3th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-6267, most recently “GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS”.

**Last updated:** 2026-07-31

## What is CVE-2026-6267?

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.

The record classifies CVE-2026-6267 under weakness class [CWE-201](https://cwe.mitre.org/data/definitions/201.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 55 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.5 — HIGH (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 26.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-29, last modified 2026-07-31

## Is CVE-2026-6267 being exploited?

No public exploitation evidence for CVE-2026-6267 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-07-31. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

- **GitLab**: GitLab

## How to fix CVE-2026-6267

No vendor patch reference has been recorded for CVE-2026-6267 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-6267

1 tracked threat in the Threadlinqs corpus references CVE-2026-6267, either in the campaign’s CVE list or as an indicator on the campaign record.

- [GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS](https://intel.threadlinqs.com/threat/TL-2026-1806) — HIGH · 2026-07-29

## Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-08-01.

**Exploit and proof of concept**

- [hackerone.com — technical description](https://hackerone.com/reports/3658324)

**Other references**

- [gitlab.com](https://gitlab.com/gitlab-org/gitlab/-/work_items/596606)
- [docs.gitlab.com](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-6267
Full detection coverage and IOCs for threats exploiting CVE-2026-6267 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp