Information disclosure via packages API authorization bypass
Published Nov 15, 2025 · Updated Nov 17, 2025
Missing authorization in affected GitLab CE/EE releases allows remote authenticated users to read branch names and pipeline details. The packages API returns package-associated branch and pipeline metadata without enforcing the project's disabled Repository setting. Reporter access to a project with a published package is sufficient; repository contents or modification capabilities are not reported.
Summary
What happened
Missing authorization in affected GitLab CE/EE releases allows remote authenticated users to read branch names and pipeline details. The packages API returns package-associated branch and pipeline metadata without enforcing the project's disabled Repository setting. Reporter access to a project with a published package is sufficient; repository contents or modification capabilities are not reported.
The record
- CVE
- CVE-2025-6171
- Published
- Nov 15, 2025
- Updated
- Nov 17, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 15, 2025CVE publishedPublication date reported by the CVE source.
- Nov 17, 2025Record 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.3.6
- Affected versionversion=18.4 <18.4.4
- Affected versionversion=18.5 <18.5.2
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.
Public exploit references
- GitLab issue reproduction procedureproof of concept · demonstrated
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