GitLab · GitLab · published 2026-06-11

CVE-2026-6976Authorization Bypass Through User-Controlled Key in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-6976 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 5% of all CVEs. This GitLab vulnerability: CVSS 3.7 (v3.1). Fixed upstream in GitLab 19.0.2, 18.11.5, 18.10.8. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.0.2, 18.11.5, 18.10.8.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.0.2, 18.11.5, 18.10.8

    Upgrade to 19.0.218.11.518.10.8

    Why: Vendor security release for server software (most severe: CVE-2026-10087).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (5th pct)FIRST EPSS v2026.06.15
CVSS base score3.7 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/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 CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to hide changes from merge request diff views due to improper input handling of file names.

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 →