CVE-2026-8472 json
Missing Authorization in GitLab
published 2026-07-08 4 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-8472 , EUVD-2026-42405
- cvss
- 4.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 33%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with minimal access permissions to read work item metadata from private projects due to missing authorization checks.
Patch / fix
- bitnami gitlab 18.11.7, 19.0.4, 19.1.2
- GitLab GitLab 18.11.7, 19.0.4, 19.1.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3615282 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.9.0, <18.11.7 >=19.0.0, <19.0.4 >=19.1.0, <19.1.2 |
18.11.7 19.0.4 19.1.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
hackerone.com
/reports/3615282
technical-description, exploit, permissions-required, web
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-1-2-released/
vendor-advisory, release-notes, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/599987
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-8472
web
Sources
- CVE List CVE-2026-8472
- NVD CVE-2026-8472
- OSV BIT-gitlab-2026-8472
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.