CVE-2026-3607 json
Access Control Check Implemented After Asset is Accessed in GitLab
published 2026-05-14 5 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-3607 , EUVD-2026-30227
- cvss
- 4.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 19%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to bypass package protection rules due to improper access control.
Patch / fix
- bitnami gitlab 18.9.7, 18.10.6, 18.11.3
- GitLab GitLab 18.9.7, 18.10.6, 18.11.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3586233 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:N/I:L/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.3.0, <18.9.7 >=18.10.0, <18.10.6 >=18.11.0, <18.11.3 |
18.9.7 18.10.6 18.11.3 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-1280 Access Control Check Implemented After Asset is Accessed
- Technology feeds
References
-
hackerone.com
/reports/3586233
technical-description, exploit, permissions-required, web
-
gitlab.com
/gitlab-org/gitlab/-/work_items/592466
broken-link, web
-
about.gitlab.com
/releases/2026/05/13/patch-release-gitlab-18-11-3-released/
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-3607
web
Sources
- CVE List CVE-2026-3607
- NVD CVE-2026-3607
- OSV BIT-gitlab-2026-3607
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.