Database/Control plane, storage & DevOps
GitLab CE/EE: planner-role user can set a future merge schedule date on their own merge requests
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
- Grafana: alert rules API returns rules from folders the user cannot readCVE-2026-13719 · Grafana (alert rules API list endpoint, folder authorization)Medium
- GitLab EE: developer-role user can influence the execution environment of Pipeline Execution Policy jobsCVE-2026-15387 · GitLab EE (Pipeline Execution Policy enforcement jobs, job dependency handling)Medium
- GitLab EE: Security Manager role can run arbitrary CI/CD jobs and read protected variablesCVE-2026-16794 · GitLab EE (compliance framework management authorization)Medium
- GitLab EE: authenticated user can view restricted group configuration settingsCVE-2026-18244 · GitLab EE (group settings page authorization)Medium
- GitLab EE: GraphQL query exposes policy configuration from an unauthorized namespaceCVE-2026-18433 · GitLab EE (GraphQL query for namespace policy configuration)Medium
- NetApp ONTAP S3 NAS bucket directory listing: An authenticated S3 user lists the contents of directories they have noCVE-2026-22052 · NetApp ONTAP S3 NAS bucket directory listingMedium
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.