How to check if you are exposed to CVE-2023-7028
- Find every GitLab CE/EE system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2023-7028.
US federal agencies had to fix this by 2024-05-22. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Timeline
- · Added to CISA's Known Exploited Vulnerabilities catalog
- · Fix-by date for US federal agencies, passed 893 days ago
Vendor advisories and fixes
Weakness type
More exploited GitLab vulnerabilities
CISA lists 6 exploited GitLab vulnerabilities. The closest matches:
- CVE-2026-97229GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound VulnerabilityAdded 2026-10-29
- CVE-2026-85706GitLab Community Edition and Enterprise Edition Path Traversal VulnerabilityAdded 2026-09-11
- CVE-2021-22175GitLab Server-Side Request Forgery (SSRF) VulnerabilityAdded 2026-02-18
- CVE-2021-39935GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) VulnerabilityAdded 2026-02-03
- CVE-2021-22205GitLab Community and Enterprise Editions Remote Code Execution VulnerabilityAdded 2021-11-03
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.
