CVE-2026-1659

criticalcovered by 1 sourcefirst seen 2026-05-13

On May 13, 2026, we released versions 18.11.3, 18.10.6, 18.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ . You can see all of GitLab release blog posts here . For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible . When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected. Security fixes Table of security fixes Title Severity Cross-site Scripting issue in Analytics dashboard chart rendering impacts GitLab EE High Cross-site Scripting issue in global search impacts GitLab CE/EE High Cross-site Scripting issue in Duo Agent output rendering impacts GitLab EE High Cross-site Scripting issue in Analytics Dashboard impacts

CSIRTS triage

What: The release contains important bug and security fixes.
Who is affected: All self-managed GitLab installations using the affected versions.
Urgency: Remediation is urgent due to the critical severity of the vulnerabilities.
Action: Upgrade to one of the patched versions immediately.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch CVE-2026-1659

Get an email if CVE-2026-1659 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Low exploitation risk0.36% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 28% of all EPSS-scored CVEs.

Advisory coverage (1)

criticalGitLab Patch Release: 18.11.3, 18.10.6, 18.9.7gitlab · 2026-05-13

External references

NVD record for CVE-2026-1659

CVE.org record

Embed the live status

— this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2026-1659 status](https://www.csirts.com/badge/CVE-2026-1659)](https://www.csirts.com/cve/CVE-2026-1659)