Confidential branch-name disclosure via issue merge-request links
Published Nov 15, 2025 · Updated Nov 17, 2025
Information disclosure in affected GitLab CE/EE releases allows remote authenticated users to view confidential branch names through project issues. The issue page renders a related merge request's source branch name without enforcing the repository's Only Project Members visibility setting. The path requires a public project, restricted repository visibility, and an issue with a related merge request; only branch names are exposed, including names derived from issue titles.
Summary
What happened
Information disclosure in affected GitLab CE/EE releases allows remote authenticated users to view confidential branch names through project issues. The issue page renders a related merge request's source branch name without enforcing the repository's Only Project Members visibility setting. The path requires a public project, restricted repository visibility, and an issue with a related merge request; only branch names are exposed, including names derived from issue titles.
The record
- CVE
- CVE-2025-7000
- Published
- Nov 15, 2025
- Updated
- Nov 17, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-201, T1213
- 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=17.6 <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.
Weakness, pattern, technique
Public exploit references
- Public 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