GitLab · GitLab · published 2026-11-17

CVE-2026-129321Insufficient Granularity of Access Control in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-129321 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This GitLab vulnerability: CVSS 4.3 (v3.1). Fixed upstream in GitLab 19.5.6, 19.4.8, 19.3.9. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.5.6, 19.4.8, 19.3.9.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.5.6, 19.4.8, 19.3.9

    Upgrade to 19.5.619.4.819.3.9

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

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (10th 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: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 CE/EE affecting all versions from 17.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with planner-role permissions to set a future merge scheduling date on merge requests they authored, a capability restricted to developer-role permissions and above, due to insufficient permission enforcement on the merge scheduling field during merge request updates.

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 →