CVE-2026-16275 json
Incorrect Authorization in GitLab
published 2026-10-13 27 d ago modified 2026-10-16 23 d ago also BIT-gitlab-2026-16275 , EUVD-2026-98223
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.4 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to read confidential notes on public projects due to incorrect authorization checks.
Patch / fix
- bitnami gitlab 19.2.8, 19.3.5, 19.4.2
- GitLab GitLab 19.2.8, 19.3.5, 19.4.2
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 25 d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3815259 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 | >=17.4.0, <19.2.8 >=19.3.0, <19.3.5 >=19.4.0, <19.4.2 |
19.2.8 19.3.5 19.4.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
hackerone.com
/reports/3815259
technical-description, exploit, permissions-required, web
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-4-2-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/606490
issue-tracking, report
-
nvd.nist.gov
/vuln/detail/CVE-2026-16275
web
Sources
- CVE List CVE-2026-16275
- NVD CVE-2026-16275
- OSV BIT-gitlab-2026-16275
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.