CVE-2026-6713 json
Incorrect Authorization in GitLab
published 2026-05-27 5 mo ago modified 2026-10-14 25 d ago also BIT-gitlab-2026-6713 , EUVD-2026-32618
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 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 unauthorized user to enumerate private projects due to incorrect authorization checks.
Patch / fix
- bitnami gitlab 18.10.7, 18.11.4, 19.0.2
- GitLab GitLab 18.10.7, 18.11.4, 19.0.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3644605 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.2.0, <18.10.7 >=18.11.0, <18.11.4 >=19.0.0, <19.0.2 |
18.10.7 18.11.4 19.0.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
hackerone.com
/reports/3644605
technical-description, exploit, permissions-required, web
-
about.gitlab.com
/releases/2026/05/27/patch-release-gitlab-19-0-1-released/
vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/597490
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-6713
web
Sources
- CVE List CVE-2026-6713
- NVD CVE-2026-6713
- OSV BIT-gitlab-2026-6713
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.