Is CVE-2026-92883 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92883 being exploited in the wild.

How severe is CVE-2026-92883?

High severity, with a CVSS score of 8.7, published 13 October 2026.

Which products and versions are affected?

GitLab Community Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1; GitLab Enterprise Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1.

Is there a fix for CVE-2026-92883?

Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-92883 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-92883?

Check whether you run GitLab Community Edition, GitLab Enterprise Edition or GitLab 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.

CVE-2026-92883: GitLab Community Edition and Enterprise Edition cross-site scripting in syntax highlighting

CVE-2026-92883 · Severity: high · CVSS 8.7 · Published 2026-10-13

GitLab is a web-based platform for managing software code repositories and CI/CD pipelines. An authenticated attacker can inject malicious JavaScript code into a repository that executes in other users' browser sessions when they view the code, potentially allowing account takeover or data theft. This requires the attacker to have repository access and a victim to view the affected code.

Technologies: GitLab Community Edition, GitLab Enterprise Edition, GitLab. Vendors: GitLab.

Quick answers

Is CVE-2026-92883 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92883 being exploited in the wild.
How severe is CVE-2026-92883?: High severity, with a CVSS score of 8.7, published 13 October 2026.
Which products and versions are affected?: GitLab Community Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1; GitLab Enterprise Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1.
Is there a fix for CVE-2026-92883?: Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92883 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-92883?: Check whether you run GitLab Community Edition, GitLab Enterprise Edition or GitLab 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.

How to fix

Fixed in: GitLab CE/EE 19.2.8, 19.3.5, 19.4.2

Technical details

A cross-site scripting vulnerability exists in GitLab's syntax highlighting output due to improper sanitization of HTML attributes. An authenticated user can craft a malicious repository that, when syntax-highlighted and viewed by other users, executes arbitrary JavaScript in their browser context. The attack requires user interaction (viewing the repository) and prior authentication by the attacker.

Affected products

GitLab Community Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1
GitLab Enterprise Edition 19.1 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1

Timeline

2026-10-13: disclosed
2026-10-12: patched: Patch releases 19.4.2, 19.3.5, 19.2.8 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.