CVE-2023-4700

LOWNVD 3.53.5—

3.5

An authorization issue affecting GitLab EE affecting all versions from 14.7 prior to 16.3.6, 16.4 prior to 16.4.2, and 16.5 prior to 16.5.1, allowed a user to run jobs in protected environments, bypassing any required approvals.

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

Published

November 6, 2023

Last Modified

November 21, 2024

References (4)

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

Vendor Advisories for CVE-2023-4700(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-5-1-released
GitLab Security
GitLab Security Release: 16.5.1, 16.4.2, 16.3.6

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 16× 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-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 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:44 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-24 14:26 UTCEG score recompute
2026-05-24 14:26 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2023-4700?

CVE-2023-4700 is a low vulnerability published on November 6, 2023. An authorization issue affecting GitLab EE affecting all versions from 14.7 prior to 16.3.6, 16.4 prior to 16.4.2, and 16.5 prior to 16.5.1, allowed a user to run jobs in protected environments, bypassing any required approvals.

When was CVE-2023-4700 disclosed?

CVE-2023-4700 was first published in the National Vulnerability Database on November 6, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-4700 actively exploited?

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

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

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

How do I remediate CVE-2023-4700?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-4700, 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-4700

Explore →

Is Your Infrastructure Affected by CVE-2023-4700?

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

Start Free Scan →Browse All CVEs

CVE-2023-4700

📅 Published

🔄 Last Modified

🔗 References (4)

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

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)