GitLab has remediated an issue in GitLab EE affecting all versions from 18.4 before 18.4.3, and 18.5 before 18.5.1 that under certain conditions could have allowed authenticated users to gain unauthorized project access by exploiting the access request approval workflow.
CVE-2025-6601
LOWNVD 2.7
2.7
- CVSS v3
- 2.7
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
October 27, 2025
Last Modified
October 28, 2025
References (3)
Vendor Advisories for CVE-2025-6601(1)
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-2025-6601?
CVE-2025-6601 is a low vulnerability published on October 27, 2025. GitLab has remediated an issue in GitLab EE affecting all versions from 18.4 before 18.4.3, and 18.5 before 18.5.1 that under certain conditions could have allowed authenticated users to gain unauthorized project access by exploiting the access request approval workflow.
When was CVE-2025-6601 disclosed?
CVE-2025-6601 was first published in the National Vulnerability Database on October 27, 2025, with the most recent update on October 28, 2025. 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-2025-6601?
CVE-2025-6601 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2025-6601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-6601, 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-2025-6601
Is Your Infrastructure Affected by CVE-2025-6601?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.