Improper access control in GitLab bypasses merge request approval policy
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
GitLab EE from 17.4 before 19.3.6, from 19.4 before 19.4.3, and from 19.5 before 19.5.1 is affected. Due to improper access control during approval rule synchronization, an authenticated user with a low-privileged account can bypass a required merge request approval policy on a protected branch under certain conditions. The weakness is classified as CWE-706. The flaw is absent from CISA KEV, and the references link a public exploit.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
Description from the CNA
GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that under certain conditions could have allowed an authenticated to bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| GitLab | GitLab | 17.4 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.1 | 19.3.6, 19.4.3, 19.5.1 | Patch available | CNA |
- GitLab VendorGitLab Affected 17.4 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.1 Fixed in 19.3.6, 19.4.3, 19.5.1 Patch available CNA
Remediation
Upgrade GitLab EE to 19.3.6, 19.4.3, or 19.5.1. CISA's SSVC data rates exploitation as none.
Written with Claude Haiku 5.5 from the sources below · 2026-10-30
- Fix · CNA GitLab (GitLab) Fixed in 19.3.6, 19.4.3, 19.5.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
GitLab 19.3.6, 19.4.3, 19.5.1
11 records Highest priority Priority LOW 11 LOW
Other records, highest priority first
- TI-2026-79058 LDAP injection in GitLab lets users take over LDAP-backed accountsPriority LOW 38
- TI-2026-79063 Cache poisoning in GitLab OAuth/OIDC discovery redirects flowsPriority LOW 32
- TI-2026-79055 Incorrect authorization in GitLab lets read_api tokens create work itemsPriority LOW 32
Timeline
- 2026-10-21 Threatist record created from CVE-2026-14288
- 2026-10-22 Alias added: GHSA-xxf3-q32p-w3cc
- 2026-10-30 CISA SSVC decision points changed
References
More Gitlab vulnerabilities
- TI-2026-71508 Integer overflow in GitLab allows code execution on the server KEVCVSS 3.1CRITICAL 10.0
- TI-2026-58817 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab KEVCVSS 3.1CRITICAL 10.0
- TI-2023-06425 Weak Password Recovery Mechanism for Forgotten Password in GitLab KEVCVSS 3.1CRITICAL 10.0
- TI-2021-05191 Code injection in GitLab KEVCVSS 3.1CRITICAL 10.0
- TI-2021-05161 Server-side request forgery in GitLab KEVCVSS 3.1CRITICAL 9.8
- TI-2022-02763 Injection in GitLab CVSS 3.1CRITICAL 9.9
Sources
- CVE-2026-14288 · CVE Program
- CVE-2026-14288 · NVD
- FIRST EPSS
- GHSA-xxf3-q32p-w3cc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences