# CVE-2026-6896: GitLab Enterprise Edition XSS in vulnerability evidence table renderer

Source: https://junglewise.ai/threats/cve-2026-6896-gitlab-enterprise-edition-xss-in-vulnerability-evidence-table  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-08. Updated: 2026-07-08  
License: CC BY 4.0 with a link back

CVE-2026-6896 · Severity: high · CVSS 8.7 · Published 2026-07-08

GitLab Enterprise Edition, a platform for software development and collaboration, contains a security flaw in how it displays vulnerability data. An attacker with developer-level access could use this flaw to run malicious scripts in the browsers of other users, such as administrators. This could lead to the theft of sensitive session information or unauthorized actions being performed on behalf of the victim.

Technologies: [GitLab Enterprise Edition](https://junglewise.ai/threats/technologies/gitlab-ee). Vendors: [GitLab](https://junglewise.ai/threats/vendors/gitlab).

## 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

## References

- [https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/)
- [https://gitlab.com/gitlab-org/gitlab/-/work_items/597887](https://gitlab.com/gitlab-org/gitlab/-/work_items/597887)
- [https://hackerone.com/reports/3682085](https://hackerone.com/reports/3682085)

## Related threats

- [GitLab EE incomplete enforcement of SAML/LDAP membership lock](https://junglewise.ai/threats/cve-2026-16255-gitlab-has-remediated-an-issue-in-gitlab-ee-affecting-all)
- [GitLab cache poisoning in OAuth/OIDC discovery](https://junglewise.ai/threats/cve-2026-112212-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab EE prompt injection in AI agent instructions](https://junglewise.ai/threats/cve-2026-96893-gitlab-has-remediated-an-issue-in-gitlab-ee-affecting-all)
- [GitLab CE/EE improper authorization in package registry](https://junglewise.ai/threats/cve-2026-5954-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab improper authorization in downstream pipeline creation](https://junglewise.ai/threats/cve-2026-16301-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)