GitLab · GitLab · published 2026-10-21

CVE-2026-14288Use of Incorrectly-Resolved Name or Reference in GitLab

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-14288 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 18% of all CVEs. This GitLab vulnerability: CVSS 3.1 (v3.1). Fixed upstream in GitLab 19.5.1, 19.4.3, 19.3.6, 19.2.9 (+3 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security fixes: 12 CVEs

    Upgrade to 19.5.119.4.319.3.619.2.919.1.919.0.1018.11.13

    Why: CVE-2026-110264: EPSS 1.3% with high severity (CVSS 10).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (18th pct)FIRST EPSS v2026.06.15
CVSS base score3.1 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →