CVE-2026-4398— Authorization Bypass Through User-Controlled Key in GitLab
Quick assessment
Affected
GitLab GitLab
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
GitLab 已修复了 GitLab EE 中的一个问题，该问题影响以下所有版本：18.3 至 19.1.7 之前、19.2 至 19.2.5 之前，以及 19.3 至 19.3.1 之前。在自管理实例中，由于缺少对命名空间的验证，在特定条件下，经过身份验证的用户可能将未授权访问的命名空间中的合规性框架分配给自己所在的项目。
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-4398
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Authorization Bypass Through User-Controlled Key in GitLab
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5
Affected Products
II. Public POCs for CVE-2026-4398
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-4398
请登录查看更多情报信息。
Patches & Fixes for CVE-2026-4398 (1)
Other References for CVE-2026-4398 (2)
Same Patch Batch · GitLab · 2026-08-27 · 3 CVEs total
| CVE-2026-75871 | 8.2 HIGH | Server-Side Request Forgery (SSRF) in GitLab AI Gateway |
| CVE-2026-19889 | 8.2 HIGH | Server-Side Request Forgery (SSRF) in GitLab AI Gateway |
IV. Related Vulnerabilities
Same product: GitLab
-
CVE-2025-10903
Loop with Unreachable Exit Condition ('Infinite Loop') in Gi -
CVE-2026-3035
Authentication Bypass Using an Alternate Path or Channel in -
CVE-2026-7487
Access Control Check Implemented After Asset is Accessed in -
CVE-2026-15387
Acceptance of Extraneous Untrusted Data With Trusted Data in -
CVE-2026-18252
Inclusion of Functionality from Untrusted Control Sphere in
Same vendor: GitLab
-
CVE-2026-75871
Server-Side Request Forgery (SSRF) in GitLab AI Gateway -
CVE-2026-19889
Server-Side Request Forgery (SSRF) in GitLab AI Gateway -
CVE-2025-10903
Loop with Unreachable Exit Condition ('Infinite Loop') in Gi -
CVE-2026-3035
Authentication Bypass Using an Alternate Path or Channel in -
CVE-2026-7487
Access Control Check Implemented After Asset is Accessed in
Same weakness: CWE-639
-
CVE-2026-81817
Flowintel Missing Task-to-Case Authorization Allows Cross-Ca -
CVE-2026-81668
Rubygem-katello: cross-tenant content view filter rule acces -
CVE-2026-17562
IDOR in Zirve Security's AdisyonPro -
CVE-2026-81658
Foreman: cross-tenant disclosure of template revisions via u -
CVE-2026-81576
Improper Authentication of Session Handles
V. Comments for CVE-2026-4398
No comments yet