What is CVE-2026-2601?
GitLab has remediated an issue in GitLab EE affecting all versions from 11.5 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects due to improper authorization checks.
The record classifies CVE-2026-2601 under weakness class CWE-862. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 154 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 4.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - EPSS (FIRST)
- 0.3% probability of exploitation in the next 30 days, higher than 24.2% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-27
Is CVE-2026-2601 being exploited?
It currently carries a trending score of 11 in the Threadlinqs vulnerability feed.
Affected products and versions
- GitLab: GitLab
How to fix CVE-2026-2601
No vendor patch reference has been recorded for CVE-2026-2601 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-2601
1 tracked threat in the Threadlinqs corpus references CVE-2026-2601, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .