Code-review evasion via mishandled file names
Published Jun 11, 2026 · Updated Jun 11, 2026
Authorization bypass in affected GitLab CE/EE versions allows remote authenticated users to hide changes from merge request diff views. Merge request diff processing improperly handles attacker-controlled file names, causing selected changes to be omitted from the review view. Exploitation requires Developer-role access and a reviewer to inspect the affected merge request; the hidden repository changes can evade code review.
Summary
What happened
Authorization bypass in affected GitLab CE/EE versions allows remote authenticated users to hide changes from merge request diff views. Merge request diff processing improperly handles attacker-controlled file names, causing selected changes to be omitted from the review view. Exploitation requires Developer-role access and a reviewer to inspect the affected merge request; the hidden repository changes can evade code review.
The record
- CVE
- CVE-2026-6976
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 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=15.9 <18.10.8
- Affected versionversion=18.11 <18.11.5
- Affected versionversion=19.0 <19.0.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
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