Vulnerability Description
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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Gitlab | Gitlab | >= 17.8.0, < 19.3.6 |
Related Weaknesses (CWE)
References
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/Release NotesVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/work_items/633147Permissions Required
FAQ
What is CVE-2026-112326?
CVE-2026-112326 is a vulnerability with a CVSS score of 3.1 (LOW). 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 authenticat...
How severe is CVE-2026-112326?
CVE-2026-112326 has been rated LOW with a CVSS base score of 3.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112326?
Check the references section above for vendor advisories and patch information. Affected products include: Gitlab Gitlab.