CVE-2026-129321
🟡 LowGitLab CE/EE · 17.8 to before 19.3.9 ; 19.4 to before 19.4.8 ; 19.5 to before 19.5.6
CVSS (Koffei note)
4.3CVSS (v3.1, CVE List)
4.3EPSS (2026-11-18)
0.198%9.66th percentile
Exploitation
No — no exploitation reported (CISA SSVC: exploitation none, automatable no, technical impact partial) ; not in KEV (cisagov mirror, 18/11/2026) ; GitLab's release post, as relayed by the Daily note of 17/11/2026, mentions no exploitation
Timeline
- 17/11/2026GitLab 19.5.6, 19.4.8 and 19.3.9 fix 37 flaws
- 17/11/2026CVE record published (CVE List)
Risk
4.3 Medium (v3.1, GitLab CNA) — AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, EPSS 0.198% (CWE-1220: Insufficient Granularity of Access Control)
Fix
Yes — 19.3.9 / 19.4.8 / 19.5.6 (GitLab patch release; GitLab.com already patched)
Official description
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CWE-1220