CVE-2026-14288
Use of Incorrectly-Resolved Name or Reference in GitLab
Reported by gitlab · Published October 21, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| gitlab | gitlab | 19.5.1, 19.4.3, 19.3.6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab | 17.4, 19.4, 19.5 |
| GitLab | GitLab | 17.4, 19.4, 19.5 |
Timeline
- Oct 21, 2026 CVE Published
- Oct 22, 2026 EPSS Score (4 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-14288
vulnetix vdb fixes CVE-2026-14288
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-14288/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- HackerOne Bug Bounty Report #3797008 technical-descriptionexploitpermissions-required