GitLab up to 19.1.6/19.2.4/19.3.0 Terminal improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 1.21- |
Summary
A vulnerability was found in GitLab up to 19.1.6/19.2.4/19.3.0. It has been classified as critical. Impacted is an unknown function of the component Terminal. This manipulation causes improper authorization. This vulnerability is registered as CVE-2026-3035. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in GitLab up to 19.1.6/19.2.4/19.3.0. Affected by this vulnerability is an unknown code block of the component Terminal. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
GitLab has remediated an issue in GitLab EE affecting all versions from 11.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 with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks.
The advisory is shared at hackerone.com. This vulnerability is known as CVE-2026-3035 since 02/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 19.1.7, 19.2.5 or 19.3.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-3029). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.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
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: GitLab 19.1.7/19.2.5/19.3.1
Timeline
02/23/2026 CVE reserved08/26/2026 Advisory disclosed
08/26/2026 VulDB entry created
08/26/2026 VulDB entry last update
Sources
Advisory: hackerone.comStatus: Confirmed
CVE: CVE-2026-3035 (🔒)
GCVE (CVE): GCVE-0-2026-3035
GCVE (VulDB): GCVE-100-395785
CERT Bund: WID-SEC-2026-3029 - GitLab: Mehrere Schwachstellen
Entry
Created: 08/26/2026 16:25Updated: 08/26/2026 21:31
Changes: 08/26/2026 16:25 (63), 08/26/2026 21:31 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.