GitLab up to 19.1.7/19.2.5/19.3.1 CI/CD Variables improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab up to 19.1.7/19.2.5/19.3.1. Impacted is an unknown function of the component CI/CD Variables. The manipulation leads to improper authorization. This vulnerability is traded as CVE-2026-79708. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in GitLab up to 19.1.7/19.2.5/19.3.1 and classified as problematic. This issue affects some unknown processing of the component CI/CD Variables. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality. The summary by CVE is:
GitLab has remediated an issue in GitLab EE affecting all versions from 19.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions could have allowed an authenticated user with developer permissions to execute a policy test pipeline on projects within their group and access protected CI/CD variables restricted to higher-privileged roles, due to insufficient scope validation.
The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2026-79708 since 08/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 346275 (GitLab 19.0 < 19.1.8 / 19.2 < 19.2.6 / 19.3 < 19.3.2 (CVE-2026-79708)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 19.1.8, 19.2.6 or 19.3.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (346275) and CERT Bund (WID-SEC-2026-3315). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source GitLab
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.5
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 346275
Nessus Name: GitLab 19.0 < 19.1.8 / 19.2 < 19.2.6 / 19.3 < 19.3.2 (CVE-2026-79708)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: GitLab 19.1.8/19.2.6/19.3.2
Timeline
08/25/2026 CVE reserved09/16/2026 Advisory disclosed
09/16/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Advisory: gitlab.comStatus: Confirmed
CVE: CVE-2026-79708 (🔒)
GCVE (CVE): GCVE-0-2026-79708
GCVE (VulDB): GCVE-100-405509
CERT Bund: WID-SEC-2026-3315 - GitLab: Mehrere Schwachstellen
Entry
Created: 09/16/2026 08:54Updated: 09/17/2026 01:47
Changes: 09/16/2026 08:54 (63), 09/17/2026 00:41 (6), 09/17/2026 01:47 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.