CVE-2026-14288BIT-GITLAB-2026-14288
Use of Incorrectly-Resolved Name or Reference in GitLab
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 19.3.6, 19.4.3, 19.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- GitLab GitLab
From 17.4 · fixed in 19.3.6; From 19.4 · fixed in 19.4.3; From 19.5 · fixed in 19.5.1
- gitlabBitnami
From 17.4.0 · fixed in 19.3.6; From 19.4.0 · fixed in 19.4.3; From 19.5.0 · fixed in 19.5.1