CVE-2025-13611: Insertion of Sensitive Information into Log File in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.5.5 and 18.6 before 18.6.3 that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions.
Other sources
GitLab has remediated an issue that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-13611?
CVE-2025-13611 is considered a medium severity vulnerability due to the potential exposure of sensitive tokens to authenticated users.
How do I fix CVE-2025-13611?
To fix CVE-2025-13611, you should upgrade to GitLab versions 18.4.5, 18.5.3, or 18.6.1 or later.
Who is affected by CVE-2025-13611?
CVE-2025-13611 affects all versions of GitLab CE/EE from 13.2 to versions prior to 18.4.5, 18.5.3, and 18.6.1.
What could be the impact of CVE-2025-13611?
The impact of CVE-2025-13611 includes the risk of unauthorized disclosure of sensitive data, specifically tokens accessible to authenticated users.
Is CVE-2025-13611 patched in the latest GitLab release?
Yes, CVE-2025-13611 has been remediated in the latest versions of GitLab, specifically in versions 18.4.5, 18.5.3, and 18.6.1.