Sensitive-token disclosure through insufficient log truncation
Published Nov 26, 2025 · Updated Mar 31, 2026
Sensitive-data exposure in GitLab CE/EE 13.2 before 18.5.5 and 18.6 before 18.6.3 allows remote authenticated users to obtain tokens from logs. The associated Gitaly fix adds log truncation, but public materials do not identify the exact logger or value path that records the tokens. Exploitation requires an authenticated user with access to affected logs, high privileges, high-complexity conditions, and user interaction.
Summary
What happened
Sensitive-data exposure in GitLab CE/EE 13.2 before 18.5.5 and 18.6 before 18.6.3 allows remote authenticated users to obtain tokens from logs. The associated Gitaly fix adds log truncation, but public materials do not identify the exact logger or value path that records the tokens. Exploitation requires an authenticated user with access to affected logs, high privileges, high-complexity conditions, and user interaction.
The record
- CVE
- CVE-2025-13611
- Published
- Nov 26, 2025
- Updated
- Mar 31, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Mar 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.2 <18.5.5
- Affected versionversion=18.6 <18.6.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo