CVE-2026-16494: GitLab · Missing Authorization
Affects gitlabSource GCVE Database
Not known to be exploited : upgrade to 19.2.2 or 19.1.4 soon.
Data as of 17 Nov 2026, 20:25 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.2.2, 19.1.4
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade gitlab to 19.2.2 or 19.1.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamigitlabpkg:bitnami/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and users should upgrade to GitLab EE versions 19.1.4 or later and 19.2.2 or later to remediate this vulnerability. Applying these official fixes will restore proper authorization checks on the project update endpoint.
Description
A missing authorization vulnerability in GitLab Enterprise Edition versions 19.1.0 through before 19.1.4 and 19.2.0 through before 19.2.2 could allow an authenticated user to modify project settings that should be restricted to higher-privileged roles. This issue arises from missing authorization checks on a project update endpoint. The vulnerability has been remediated in versions 19.1.4 and 19.2.2.