Skip to main content
CISA Known Exploited Vulnerabilities

GitLab Community and Enterprise Editions Improper Access Control Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2024-05-01
Remediation due
2024-05-22

Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes
https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/ ; https://nvd.nist.gov/vuln/detail/CVE-2023-7028

Description

An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2023-7028 to the KEV catalog 110 days after its CVE record was published. The median for entries added in 2024 is 21.5 days.
  • It is one of 6 GitLab entries in the CISA KEV catalog, and the only one added in 2024.
  • Its current EPSS score (94.5%) is higher than that of 77% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score10.0 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableyes
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
3 days
and forensic triage
KEV due date
2024-05-22
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact total, 2024-05-02).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
GitLab
GitLab
16.1 to <16.1.6
16.2 to <16.2.9
16.3 to <16.3.7
16.4 to <16.4.5
16.5 to <16.5.6
16.6 to <16.6.4
16.7 to <16.7.2

Solutions and Workarounds

from the CNA's CVE record

Solution

Upgrade to versions 16.7.2, 16.6.4, 16.5.6, 16.4.5, 16.3.7, 16.2.9, 16.1.6 or above.

References

3 links

Record Details

Published
2024-01-12
Last updated
2026-08-15
Assigner (CNA)
GitLab
Credited to
Thanks [asterion04](https://hackerone.com/asterion04) for reporting this vulnerability through our HackerOne bug bounty program

More from GitLab

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.