CVE-2023-2030

LOWNVD 3.53.5—

3.5

An issue has been discovered in GitLab CE/EE affecting all versions from 12.2 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which an attacker could potentially modify the metadata of signed commits.

CVSS v3: 3.5
EG Score: 3.5(medium)
EPSS: 14.1%
KEV: Not listed

Published

January 12, 2024

Last Modified

March 20, 2025

References (4)

cve@gitlabhttps://gitlab.com/gitlab-org/gitlab/-/issues/407252
cve@gitlabhttps://hackerone.com/reports/1929929
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab/-/issues/407252
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/1929929

Vendor Advisories for CVE-2023-2030(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

patch-release-gitlab-16-7-2-released
GitLab Security
GitLab Critical Security Release: 16.7.2, 16.6.4, 16.5.6

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 10:27 UTCEG score recompute

Frequently asked(5)

What is CVE-2023-2030?

CVE-2023-2030 is a low vulnerability published on January 12, 2024. An issue has been discovered in GitLab CE/EE affecting all versions from 12.2 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which an attacker could potentially modify the metadata of signed commits.

When was CVE-2023-2030 disclosed?

CVE-2023-2030 was first published in the National Vulnerability Database on January 12, 2024, with the most recent update on March 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-2030 actively exploited?

CVE-2023-2030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2023-2030?

CVE-2023-2030 has a CVSS v3 base score of 3.5 (NVD).

How do I remediate CVE-2023-2030?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-2030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-2030

Explore →

Is Your Infrastructure Affected by CVE-2023-2030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2023-2030

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2023-2030(1)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)