CVE-2026-4398

published 27 Aug 2026 · updated 28 Aug 2026

Authorization Bypass Through User-Controlled Key in GitLab

6.4MediumCVSS 5.4EPSS 0%2 public exploits

2 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in GitLab 19.1.7, GitLab 19.2.5 and GitLab 19.3.1.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
GitLabGitLab>=18.3 <19.1.7, >=19.2 <19.2.5, >=19.3 <19.3.119.1.7, 19.2.5, 19.3.1

Exploit evidence

2 public sources

Vendor advisories

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in GitLab, strongest first

10.0CriticalPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-4398 severity on Zeptric[![CVE-2026-4398](https://zeptric.io/badge/cve/CVE-2026-4398.svg)](https://zeptric.io/cve/CVE-2026-4398)