CVE-2026-112326
Improper Cleanup on Thrown Exception in GitLab
Reported by gitlab · Published October 21, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| GitLab | GitLab | 19.5.1, 19.4.3, 19.3.6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab | 17.8, 19.4, 19.5 |
| GitLab | GitLab | 17.8, 19.4, 19.5 |
Timeline
- Oct 21, 2026 CVE Published
- Oct 22, 2026 EPSS Score (3 in total, the first dated here)
- Oct 22, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-112326
vulnetix vdb fixes CVE-2026-112326Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-112326/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart