Skip to content
Fencer Vulns
low 3.1

CVE-2026-112326 json

Improper Cleanup on Thrown Exception in GitLab

published 2026-10-21 18 d ago modified 2026-11-04 4 d ago also BIT-gitlab-2026-112326 , EUVD-2026-107670

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami gitlab 19.3.6, 19.4.3, 19.5.1
  • GitLab GitLab 19.3.6, 19.4.3, 19.5.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=17.8.0, <19.3.6
>=19.4.0, <19.4.3
>=19.5.0, <19.5.1
19.3.6
19.4.3
19.5.1

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-460 Improper Cleanup on Thrown Exception
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.