GitLab · GitLab · published 2026-07-29
CVE-2026-6267Insertion of Sensitive Information Into Sent Data in GitLab
Routine No exploitation evidence; EPSS 0.6%.
CVE-2026-6267 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 50% of all CVEs. This GitLab vulnerability: CVSS 8.5 (v3.1), a successful attack gives total control of the component. Fixed upstream in GitLab 19.2.1, 19.1.3, 19.0.5. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in GitLab 19.2.1, 19.1.3, 19.0.5.
Patch events
DevOpsGitLab
GitLab security releases: 19.2.1, 19.1.3, 19.0.5
Upgrade to
19.2.119.1.319.0.5Why: CVE-2026-6336: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.6% (50th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.5 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- GitLab GitLab
10.1.0to before19.0.5(affected)19.1to before19.1.3(affected)19.2to before19.2.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.