EUVD-2026-20799
GHSA-76v4-rwr7-cgr3
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Lifecycle Timeline
4DescriptionCVE.org
GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that under certain circumstances could have allowed an authenticated user with auditor privileges to modify vulnerability flag data in private projects due to incorrect authorization.
AnalysisAI
GitLab EE versions 18.6-18.8.8, 18.9-18.9.4, and 18.10-18.10.2 allow authenticated users with auditor role privileges to modify vulnerability flag data in private projects due to improper authorization checks. The vulnerability requires valid GitLab credentials and auditor-level access but enables unauthorized data integrity compromise within project security contexts.
Technical ContextAI
This vulnerability stems from an authorization bypass (CWE-863: Incorrect Authorization) in GitLab's access control layer governing vulnerability flag management. The vulnerability affects GitLab Enterprise Edition's privilege model, where auditor-role users are granted elevated permissions for security monitoring. The root cause is a logic flaw that fails to properly validate whether an auditor's read/audit permissions extend to modification of vulnerability flags-a sensitive operation that should be restricted to project maintainers or owners. The bug manifests in the API or web interface endpoints responsible for updating vulnerability flag status or metadata within private projects.
RemediationAI
Vendor-released patch: GitLab EE 18.8.9, 18.9.5, and 18.10.3 or later. Upgrade immediately to one of these patched versions according to your deployment track. Organizations unable to patch immediately should audit auditor role assignments and restrict auditor account usage to trusted personnel only. Review GitLab's security release notes at https://about.gitlab.com/releases/2026/04/08/patch-release-gitlab-18-10-3-released/ for detailed upgrade guidance. Monitor vulnerability flag modification logs for unauthorized changes by auditor accounts.
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today