CVE-2026-7487 json
Access Control Check Implemented After Asset is Accessed in GitLab
published 2mo ago modified 2mo ago also BIT-gitlab-2026-7487 , EUVD-2026-66430
- cvss
- 3.5
- 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 24%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.
Patch / fix
- bitnami gitlab 19.1.7, 19.2.5, 19.3.1
- GitLab GitLab 19.1.7, 19.2.5, 19.3.1
Is CVE-2026-7487 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3669140 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N |
| OSV | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=13.1.0, <19.1.7 >=19.2.0, <19.2.5 >=19.3.0, <19.3.1 |
19.1.7 19.2.5 19.3.1 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-1280 Access Control Check Implemented After Asset is Accessed
- Technology feeds
References
-
hackerone.com
/reports/3669140
technical-description, exploit, permissions-required, third-party-advisory, advisory
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-3-1-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/598657
issue-tracking, permissions-required, report
-
nvd.nist.gov
/vuln/detail/CVE-2026-7487
web
Sources
- CVE List CVE-2026-7487
- NVD CVE-2026-7487
- OSV BIT-gitlab-2026-7487
Fencer Intel 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.