Read the docs
TI-2026-79064 Aliases CVE-2026-112326GHSA-h7pg-g89w-v3vj

GitLab read-only users can delete vulnerability records

Priority LOW 15CWE-460Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

GitLab EE from 17.8 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 is affected. Improper cleanup logic during error handling fails to distinguish pre-existing vulnerability records from newly created ones (CWE-460). Under certain conditions, an authenticated user with read-only permissions can permanently delete existing vulnerability records.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00197 9th percentileScored 2026-11-07
Fix Fixed GitLab (GitLab): 19.3.6, 19.4.3, 19.5.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GitLabGitLab17.8 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.119.3.6, 19.4.3, 19.5.1Patch availableCNA
  • GitLab VendorGitLab Affected 17.8 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.1 Fixed in 19.3.6, 19.4.3, 19.5.1 Patch available CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*17.8.0 to before 19.3.6; 19.4.0 to before 19.4.3VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*19.5.0VulnerableGitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* Versions 17.8.0 to before 19.3.6; 19.4.0 to before 19.4.3 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:* Versions 19.5.0 Vulnerable ·GitLab

Remediation

Upgrade GitLab to 19.3.6, 19.4.3, or 19.5.1, depending on the release branch in use.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA GitLab (GitLab) Fixed in 19.3.6, 19.4.3, 19.5.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    GitLab 19.3.6, 19.4.3, 19.5.1

    11 records Highest priority Priority LOW 11 LOW

    Other records, highest priority first

    • TI-2026-79058 LDAP injection in GitLab lets users take over LDAP-backed accountsPriority LOW 38
    • TI-2026-79063 Cache poisoning in GitLab OAuth/OIDC discovery redirects flowsPriority LOW 32
    • TI-2026-79055 Incorrect authorization in GitLab lets read_api tokens create work itemsPriority LOW 32
    Show all 11 records →

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-112326
  2. 2026-10-22 Alias added: GHSA-h7pg-g89w-v3vj
  3. 2026-10-30 CISA SSVC decision points changed

References

Advisory 1

Other 1

  • TI-2026-71508 Integer overflow in GitLab allows code execution on the server KEVCVSS 3.1CRITICAL 10.0
  • TI-2026-58817 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2023-06425 Weak Password Recovery Mechanism for Forgotten Password in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05191 Code injection in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05161 Server-side request forgery in GitLab KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-02763 Injection in GitLab CVSS 3.1CRITICAL 9.9
See all 1506 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences