CVE-2025-13611
CVSS 2.0 LowEPSS 0.0%
- CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
- Published: 2025-11-26T20:15:49.193
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2025-13611
CVE-2025-13611 is a low severity vulnerability affecting the affected product.
Description: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions. Related CVE by CWENo related CWE found.Top CVE for VendorNo vendor taxonomy on this […]
Exploit Difficulty: VERY HARD
⏱️ Time to exploit: Days or weeks
🛠️ Required skills: Expert-level security skills
💰 Public exploits: Not publicly available
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Description: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions. Related CVE by CWENo related CWE found.Top CVE for VendorNo vendor taxonomy on this […]
Exploit Difficulty: VERY HARD
⏱️ Time to exploit: Days or weeks
🛠️ Required skills: Expert-level security skills
💰 Public exploits: Not publicly available
How to Fix:
1 Identify affected systems
- Check if you're running the affected product
2 Immediate actions
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
VERY HARD
Time to Exploit: Days or weeks
Skills Required: Expert-level security skills
Public Exploits: Not publicly available
Vulnerability Timeline
Nov 26, 2025
Vulnerability Published
CVE details first published to NVD database
Nov 26, 2025
Imported to Database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.