CVE-2026-4398 json
Authorization Bypass Through User-Controlled Key in GitLab
published 7mo ago modified last mo. also BIT-gitlab-2026-4398 , EUVD-2026-67167
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
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-4398 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.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3549150 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=18.3.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-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
-
hackerone.com
/reports/3549150
technical-description, exploit, permissions-required, web
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-3-1-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/600360
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-4398
web
Sources
- CVE List CVE-2026-4398
- NVD CVE-2026-4398
- OSV BIT-gitlab-2026-4398
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.