Authenticated browser script execution via unsanitized diff paths
Published Sep 29, 2026 · Updated Sep 29, 2026
Cross-site scripting in GitLab CE/EE allows remote authenticated users to run JavaScript in another user's browser through a merge request diff. The diff viewer fails to sanitize path components before displaying them, allowing a crafted path to execute as script in the viewer's session. Exploitation requires an authenticated attacker and a separate user to view the affected merge request diff.
Summary
What happened
Cross-site scripting in GitLab CE/EE allows remote authenticated users to run JavaScript in another user's browser through a merge request diff. The diff viewer fails to sanitize path components before displaying them, allowing a crafted path to execute as script in the viewer's session. Exploitation requires an authenticated attacker and a separate user to view the affected merge request diff.
The record
- CVE
- CVE-2026-84739
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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 <19.2.7
- Affected versionversion=19.3 <19.3.3
- Affected versionversion=19.4 <19.4.1
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started