Exploited CVEs / GitLab / CVE-2023-7028

CVE-2023-7028

GitLab Community and Enterprise Editions Improper Access Control Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2024-05-22 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: GitLab Releases (security), linked below.

Risk summary

CriticalCISA KEV

9.8

CVSS v3 base

95%

EPSS exploit probability

Critical

Severity

2024-05-01

Added to KEV

2024-05-22 (past due)

CISA due date

Actively exploited GitLab CE/EE vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2024-05-01.

Senserva AI read on CVE-2023-7028 CISA required action Official fix for CVE-2023-7028 Admin questions

Senserva AI Opinion for CVE-2023-7028

GitLab's password reset flow could be tricked into sending the reset email to an attacker-controlled, unverified address, turning account takeover into a single web request. It is among the most elegant authentication failures in recent memory: no exploit code, just a logic flaw, hence the 95 percent EPSS and CVSS 9.8. Self-managed GitLab CE and EE instances were exploited in the wild before its May 2024 KEV entry.

Do this: Patch self-managed GitLab, enforce two-factor authentication which blocks this takeover path, and audit password reset events for addresses that do not belong to your users.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2023-7028

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2023-7028, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2023-7028.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed once a day (early morning US Central)):
- CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control Vulnerability
- Affected: GitLab CE/EE
- Severity: Critical, CVSS v3 9.8; EPSS 30-day exploitation probability 95%
- Added to CISA KEV: 2024-05-01; federal remediation due 2024-05-22
- Ransomware-linked: no
- CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: GitLab Releases (security).

Do this now: Federal remediation deadline 2024-05-22; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated September 13, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2023-7028

Published: 2024-05-01
Last revised: 2024-05-01
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2024-05-01 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 95.0%
2026-07-24 EPSS 95.0% to 94.7%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2024-05-22 (past due).

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

Official fix for CVE-2023-7028

The authoritative fix and affected-version list are published by the vendor. Find the GitLab CE/EE advisory on GitLab Releases (security).

GitLab Releases (security)CISA KEV entry

Common questions about CVE-2023-7028

Is CVE-2023-7028 actively exploited?

Yes. CVE-2023-7028 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2024-05-01, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 95%.

What is the CISA deadline and required action for CVE-2023-7028?

CISA set the federal (BOD 22-01) remediation due date at 2024-05-22, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2023-7028?

The authoritative fix is in the vendor advisory: see GitLab Releases (security) for the patched GitLab CE/EE versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2023-7028?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2023-7028's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed once a day (early morning US Central).

Scope and sources

More exploited GitLab CVEs: CVE-2026-85706 CVE-2021-22175 CVE-2021-39935 CVE-2021-22205
All GitLab exploited CVEs on one page: GitLab vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.