Cross-user script execution via unsanitized evidence rendering
Published Jul 8, 2026 · Updated Jul 8, 2026
Cross-site scripting in affected GitLab EE releases allows remote authenticated users to execute scripts in other users' browser sessions. The vulnerability evidence table renderer fails to sanitize user-supplied input before inserting it into rendered content. Developer-role access is required to supply the payload, and another user must view the affected evidence table for the script to run.
Summary
What happened
Cross-site scripting in affected GitLab EE releases allows remote authenticated users to execute scripts in other users' browser sessions. The vulnerability evidence table renderer fails to sanitize user-supplied input before inserting it into rendered content. Developer-role access is required to supply the payload, and another user must view the affected evidence table for the script to run.
The record
- CVE
- CVE-2026-6896
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 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.11 <18.11.7
- Affected versionversion=19.0 <19.0.4
- Affected versionversion=19.1 <19.1.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