GitLab · GitLab · published 2026-08-27
CVE-2026-4398Authorization Bypass Through User-Controlled Key in GitLab
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-4398 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% of all CVEs. This GitLab vulnerability: CVSS 5.4 (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.2% (16th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.4 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
18.3to 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 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.
Quoted from the CVE Program record.