CVE-2023-3401

MEDIUMNVD 4.8
4.8

An issue has been discovered in GitLab affecting all versions before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. The main branch of a repository with a specially designed name allows an attacker to create repositories with malicious code.

CVSS v3
4.8
EG Score
EPSS
KEV
Not listed

Published

August 2, 2023

Last Modified

November 21, 2024

Vendor Advisories for CVE-2023-3401(2)

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

Frequently asked(4)

What is CVE-2023-3401?
CVE-2023-3401 is a medium vulnerability published on August 2, 2023. An issue has been discovered in GitLab affecting all versions before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. The main branch of a repository with a specially designed name allows an attacker to create repositories with malicious code.
When was CVE-2023-3401 disclosed?
CVE-2023-3401 was first published in the National Vulnerability Database on August 2, 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.
What is the CVSS score of CVE-2023-3401?
CVE-2023-3401 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2023-3401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-3401, 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-3401

Explore →

Is Your Infrastructure Affected by CVE-2023-3401?

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