GitLab has remediated an issue in GitLab EE affecting all versions from 17.8 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an authenticated user with read-only permissions to permanently delete existing vulnerability records due to improper cleanup logic that failed to distinguish between pre-existing records from newly created ones during error handling.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ Release Notes, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 6
- Cpes+2 CPE criteria (now 2)NVD modified 2026-10-27 14:08
- StatusAwaiting Analysis → AnalyzedNVD modified 2026-10-27 14:08
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-22 16:18
- Cpes-1 CPE criteria (now 0)NVD modified 2026-10-22 01:16
- StatusPublished → ReceivedNVD modified 2026-10-22 01:16
- First seenCVSS 3.1 · gitlabNVD modified 2026-10-21 23:33
Affected (CPE criteria) 2
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*
References 2
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ Release Notes, Vendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/work_items/633147 Permissions Required