CVE-2026-4398
Authorization Bypass Through User-Controlled Key in GitLab
Description
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.
INFO
Published Date :
April 8, 2026, 11:16 p.m.
Last Modified :
Aug. 28, 2026, 4:18 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Consult the CVE Numbering Authority for details.
- Review CNA's rejection reasoning.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-4398.
| URL | Resource |
|---|---|
| https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/ | |
| https://gitlab.com/gitlab-org/gitlab/-/work_items/600360 | |
| https://hackerone.com/reports/3549150 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-4398 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-4398
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-4398 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-4398 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 28, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-4398', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-08-28T13:58:41.461501Z'} -
CVE Unrejected by [email protected]
Aug. 27, 2026
Action Type Old Value New Value -
CVE Modified by [email protected]
Aug. 27, 2026
Action Type Old Value New Value Changed Description Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. 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. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Added CWE CWE-639 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/4xxx/CVE-2026-4398.json">CVE-2026-4398</a> Added Reference https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/ Added Reference https://gitlab.com/gitlab-org/gitlab/-/work_items/600360 Added Reference https://hackerone.com/reports/3549150 -
CVE Rejected by [email protected]
Apr. 08, 2026
Action Type Old Value New Value -
New CVE Received by [email protected]
Apr. 08, 2026
Action Type Old Value New Value Added Description Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.