Quick answers
- Is CVE-2026-6896 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6896 being exploited in the wild.
- How severe is CVE-2026-6896?
- High severity, with a CVSS score of 8.7, published 8 July 2026.
- Which products and versions are affected?
- GitLab Enterprise Edition 13.11 to 18.11.7, 19.0 to 19.0.4, 19.1 to 19.1.2.
- Is there a fix for CVE-2026-6896?
- A patch was published on 2026-07-08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6896 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-6896?
- Check whether you run GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored cross-site scripting (XSS) vulnerability exists in GitLab Enterprise Edition (EE) within the vulnerability evidence table renderer. The issue stems from improper sanitization of user-supplied input when generating the evidence table. An authenticated attacker with at least 'developer' role permissions can inject malicious scripts that execute in the context of another user's browser session when they view the affected page. This vulnerability is tracked as CVE-2026-6896 and carries a CVSS score of 8.7 due to the potential for session hijacking and the scope change (S:C). GitLab has released patches in versions 18.11.7, 19.0.4, and 19.1.2 to address this issue.
Affected products
- GitLab GitLab Enterprise Edition 13.11 to 18.11.7, 19.0 to 19.0.4, 19.1 to 19.1.2
Timeline
- 2026-07-08: disclosed
- 2026-07-08: patched