GitLab up to 19.3.8/19.4.7/19.5.5 Merge Scheduling permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in GitLab up to 19.3.8/19.4.7/19.5.5. It has been rated as problematic. This issue affects some unknown processing of the component Merge Scheduling. The manipulation leads to permission. This vulnerability is traded as CVE-2026-129321. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, has been found in GitLab up to 19.3.8/19.4.7/19.5.5. This issue affects an unknown function of the component Merge Scheduling. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is integrity. The summary by CVE is:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with planner-role permissions to set a future merge scheduling date on merge requests they authored, a capability restricted to developer-role permissions and above, due to insufficient permission enforcement on the merge scheduling field during merge request updates.
The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2026-129321 since 11/14/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 T1222 for this issue.
Upgrading to version 19.3.9, 19.4.8 or 19.5.6 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 19.3.0
- 19.3.1
- 19.3.2
- 19.3.3
- 19.3.4
- 19.3.5
- 19.3.6
- 19.3.7
- 19.3.8
- 19.4.0
- 19.4.1
- 19.4.2
- 19.4.3
- 19.4.4
- 19.4.5
- 19.4.6
- 19.4.7
- 19.5.0
- 19.5.1
- 19.5.2
- 19.5.3
- 19.5.4
- 19.5.5
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
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: PermissionCWE: CWE-275 / 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.3.9/19.4.8/19.5.6
Timeline
11/14/2026 CVE reserved11/17/2026 Advisory disclosed
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Advisory: gitlab.comStatus: Confirmed
CNA: GitLab
CVE: CVE-2026-129321 (🔒)
GCVE (CVE): GCVE-0-2026-129321
GCVE (VulDB): GCVE-100-437969
Entry
Created: 11/17/2026 05:37Changes: 11/17/2026 05:37 (63)
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.