An issue has been discovered in GitLab CE/EE affecting all versions from 15.7 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed authenticated users with developer access to obtain ID tokens for protected branches under certain circumstances.
CVE-2025-5819
MEDIUMNVD 5.0
5.0
- CVSS v3
- 5.0
- EG Score
- —
- EPSS
- —
- KEV
- Not listed
Published
August 13, 2025
Last Modified
August 29, 2025
References (2)
Vendor Advisories for CVE-2025-5819(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-5819?
CVE-2025-5819 is a medium vulnerability published on August 13, 2025. An issue has been discovered in GitLab CE/EE affecting all versions from 15.7 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed authenticated users with developer access to obtain ID tokens for protected branches under certain circumstances.
When was CVE-2025-5819 disclosed?
CVE-2025-5819 was first published in the National Vulnerability Database on August 13, 2025, with the most recent update on August 29, 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-5819?
CVE-2025-5819 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2025-5819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5819, 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-5819
Is Your Infrastructure Affected by CVE-2025-5819?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.