GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: authenticated user can create issues with locked discussions without the required permission

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

Impact

Under certain conditions, an authenticated user can create issues with the discussion locked even though their role should not allow it, because an authorization check is missing. The impact is limited to integrity: it changes issue metadata on a self-hosted GitLab that may also run the fleet's CI/CD. The record describes no data exposure and no code execution.

Who can reach it

Any authenticated GitLab user. Network access to the GitLab instance is required.

What to do

Upgrade GitLab CE/EE to 19.3.9, 19.4.8 or 19.5.6, according to your release line. All versions from 14.0 are affected. Upgrading a self-managed instance restarts the GitLab services. GitLab.com is already patched.

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.