GitLab · GitLab · published 2026-10-21

CVE-2026-103515Incorrect Authorization in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-103515 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This GitLab vulnerability: CVSS 2.7 (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.2% (14th pct)FIRST EPSS v2026.06.15
CVSS base score2.7 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:H/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 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.

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 →