GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: planner-role user can set a future merge schedule date on their own merge requests

CVSS 4.3CVE-2026-129321Control plane, storage & DevOpscurated

Impact

Permissions on the merge scheduling field are not enforced during merge request updates. A user with Planner role can set a future merge date on merge requests they authored, which should require Developer role or higher. The impact is limited to integrity and confined to their own merge requests.

Who can reach it

An authenticated GitLab user with Planner role who authored the merge request. Network access to the instance is required.

What to do

Upgrade GitLab CE/EE to 19.3.9, 19.4.8 or 19.5.6. Versions from 17.8 are affected. Upgrading a self-managed instance restarts the GitLab services.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.