VulnerabilityPublished 29 Jun 2026Updated 8 Sep 2026

CVE-2026-0934: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

Compare

Not known to be exploited · fixed in 19.1.1 : update gitlab when convenient.

Data as of 12 Nov 2026, 23:24 UTC

Severity

Low

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.1.1, 19.0.3, 18.11.6

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 19.1.1, 19.0.3 or 18.11.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=17.9.0 <18.11.6 >=19.0.0 <19.0.3 >=19.1.0 <19.1.1	Fixed in 18.11.6 19.0.3 19.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade affected GitLab EE instances to versions 18.11.6 or later for the 17.9 series, 19.0.3 or later for the 19.0 series, and 19.1.1 or later for the 19.1 series to remediate this vulnerability.

Description

GitLab EE versions from 17.9 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an authorization vulnerability. Under certain conditions, authenticated users with custom role permissions could view, create, or delete protected environment configurations even when CI/CD visibility was disabled for the project. This issue has been remediated in the specified fixed versions.

Impact

Authenticated users with custom role permissions could improperly view, create, or delete protected environment configurations despite CI/CD visibility being disabled, potentially leading to unauthorized changes in protected environments. The severity is rated low, indicating limited impact or exploitability.

Summary

An authorization vulnerability (CVE-2026-0934) in GitLab EE allowed authenticated users with custom role permissions to bypass CI/CD visibility restrictions and access protected environment configurations. The flaw affected versions >=17.9.0 <18.11.6, >=19.0.0 <19.0.3, and >=19.1.0 <19.1.1. The issue has been fixed in versions 18.11.6, 19.0.3, and 19.1.1 respectively.

References

Community reviews

Loading reviews…