Skip to content
Server Security Center
KEVcritical10.0

CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control

GitLab CE/EE · listed in the CISA catalog of actively exploited vulnerabilities since 2024-05-01.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
95%
higher than 99.8% of all CVEs
Added to CISA KEV
2024-05-01
US federal due date 2024-05-22
Ubuntu priority
medium

CVE-2023-7028 explained

CVE-2023-7028 is an improper access control flaw in GitLab CE/EE. Password reset emails for user accounts could be delivered to an unverified email address. This can let someone other than the account owner reset a password and take over the account. CISA lists it as known to be exploited.

Impact

An unauthenticated attacker can act over the network with low complexity and no user interaction. Because reset emails can reach an unverified address, the attacker can take control of user accounts. The CVSS vector rates confidentiality and integrity impact as high, availability as unaffected, and scope as changed. The impact can therefore extend beyond the GitLab instance itself.

Who is affected

Upstream, GitLab CE/EE is affected from 16.1 before 16.1.6, 16.2 before 16.2.9, 16.3 before 16.3.7, 16.4 before 16.4.5, 16.5 before 16.5.6, 16.6 before 16.6.4, and 16.7 before 16.7.2. In Ubuntu, the gitlab source package in Ubuntu 16.04 LTS is listed as affected. No fixed version has been published in the standard archive. Ubuntu 16.04 LTS is end of life.

Written with AI from the data on this page and checked against it automatically.

Official 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.

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

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • GitLab
    Affected
    • ≥ 16.1, < 16.1.6
    • ≥ 16.2, < 16.2.9
    • ≥ 16.3, < 16.3.7
    • ≥ 16.4, < 16.4.5
    • ≥ 16.5, < 16.5.6
    • ≥ 16.6, < 16.6.4
    • ≥ 16.7, < 16.7.2
    Fixed in
    • 16.1.6
    • 16.2.9
    • 16.3.7
    • 16.4.5
    • 16.5.6
    • 16.6.4
    • 16.7.2

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify any systems running the gitlab package from Ubuntu 16.04 LTS, or other GitLab CE/EE installations.
  2. Upgrade to a GitLab CE/EE version at or above the fixed upstream release for your branch, following vendor instructions.
  3. Upgrade or migrate Ubuntu 16.04 LTS systems to a supported release, because this release is end of life.
  4. Restart GitLab services after updating so the fixed code is running.
  5. Review account password reset activity and registered email addresses for signs of unauthorized changes.

Ubuntu 16.04 LTS is end of life, and its gitlab package has no fix. Do not wait for one. Migrate to a supported, upstream-fixed GitLab version. Until then, restrict network access to the instance to trusted users. If you cannot apply mitigations, CISA advises discontinuing use of the product.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace gitlab with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="gitlab"'

No fixed version available

No Ubuntu or Debian release has published a fixed version of gitlab yet, so every installed version is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: about.gitlab.com/releases/2024/01/11/critical-security-re…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-640 Weak Password Recovery Mechanism for Forgotten Password

Questions about CVE-2023-7028

Is CVE-2023-7028 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-05-01, with a US federal due date of 2024-05-22. Whether it has been used in ransomware campaigns is listed as unknown.
Will Ubuntu publish a fixed gitlab package for Ubuntu 16.04 LTS?
No fixed version has been published, and Ubuntu 16.04 LTS is end of life. Move to a supported platform and a fixed upstream GitLab version.
Does an attacker need an account or user interaction?
No. According to the CVSS vector, no privileges and no user interaction are required, and the attack works over the network.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.