GitLab · GitLab · published 2026-07-29

CVE-2026-14351Exposure of Sensitive Information Through Metadata in GitLab

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-14351 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 35% of all CVEs. This GitLab vulnerability: CVSS 4.3 (v3.1). Fixed upstream in GitLab 19.2.1, 19.1.3, 19.0.5. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.2.1, 19.1.3, 19.0.5.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.2.1, 19.1.3, 19.0.5

    Upgrade to 19.2.119.1.319.0.5

    Why: CVE-2026-6336: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (35th pct)FIRST EPSS v2026.06.15
CVSS base score4.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 CE/EE affecting all versions from 8.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthenticated user to view the title of a confidential issue through a publicly accessible merge request due to improper authorization checks.

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 →