GitLab · GitLab · published 2026-08-26
CVE-2026-7487Access Control Check Implemented After Asset is Accessed in GitLab
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-7487 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 25% of all CVEs. This GitLab vulnerability: CVSS 3.5 (v3.1). Fixed upstream in GitLab 19.3.1, 19.2.5, 19.1.7. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in GitLab 19.3.1, 19.2.5, 19.1.7.
Patch events
DevOpsGitLab
GitLab security releases: 19.3.1, 19.2.5, 19.1.7
Upgrade to
19.3.119.2.519.1.7Why: Vendor security release for server software (most severe: CVE-2026-18252).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (25th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- GitLab GitLab
13.1to before19.1.7(affected)19.2to before19.2.5(affected)19.3to before19.3.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.