GitLab vulnerabilities: known CVEs & security history
GitLab · Infrastructure · 37 tracked CVEs · 1 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all GitLab release lines — 37 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check GitLab's current status and the safe version to run.
Known GitLab CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2021-22205⚡ exploited | critical | 10 | 100% | 2021 |
| CVE-2026-6896 | high | 8.7 | 0% | 2026 |
| CVE-2026-10086 | high | 8.7 | 0% | 2026 |
| CVE-2025-9222 | high | 8.7 | 0% | 2026 |
| CVE-2026-12053 | high | 8.6 | 0% | 2026 |
| CVE-2026-5173 | high | 8.5 | 0% | 2026 |
| CVE-2026-2370 | high | 8.1 | 0% | 2026 |
| CVE-2026-10712 | high | 8 | 0% | 2026 |
| CVE-2025-13761 | high | 8 | 1% | 2026 |
| CVE-2026-1092 | high | 7.5 | 1% | 2026 |
| CVE-2025-12664 | high | 7.5 | 1% | 2026 |
| CVE-2026-13320 | high | 7.3 | 0% | 2026 |
| CVE-2025-13772 | high | 7.1 | 0% | 2026 |
| CVE-2026-1101 | medium | 6.5 | 0% | 2026 |
| CVE-2026-1516 | medium | 5.7 | 0% | 2026 |
| CVE-2026-5309 | medium | 5.4 | 0% | 2026 |
| CVE-2026-4332 | medium | 5.4 | 0% | 2026 |
| CVE-2026-2238 | medium | 5.3 | 0% | 2026 |
| CVE-2026-11379 | medium | 5.3 | 0% | 2026 |
| CVE-2026-11827 | medium | 4.9 | 0% | 2026 |
| CVE-2026-8330 | medium | 4.4 | 0% | 2026 |
| CVE-2026-8472 | medium | 4.3 | 0% | 2026 |
| CVE-2026-7492 | medium | 4.3 | 0% | 2026 |
| CVE-2026-5952 | medium | 4.3 | 0% | 2026 |
| CVE-2026-5796 | medium | 4.3 | 0% | 2026 |
| CVE-2026-1606 | medium | 4.3 | 0% | 2026 |
| CVE-2026-2619 | medium | 4.3 | 0% | 2026 |
| CVE-2026-2104 | medium | 4.3 | 0% | 2026 |
| CVE-2026-1752 | medium | 4.3 | 0% | 2026 |
| CVE-2025-9484 | medium | 4.3 | 0% | 2026 |
| CVE-2026-0934 | low | 3.8 | 0% | 2026 |
| CVE-2025-12506 | low | 3.5 | 0% | 2026 |
| CVE-2026-3176 | low | 3.1 | 0% | 2026 |
| CVE-2026-6352 | low | 2.7 | 0% | 2026 |
| CVE-2026-13151 | low | 2.7 | 0% | 2026 |
| CVE-2026-4916 | low | 2.7 | 0% | 2026 |
| CVE-2026-12635 | none | 0 | 0% | 2026 |
Is my GitLab version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your GitLab version → · Monitor GitLab for new CVEs →
GitLab vulnerabilities — frequently asked
How many known vulnerabilities does GitLab have?
IsItPatched tracks 37 CVEs for GitLab, 1 of which is actively exploited (CISA KEV). 1 is critical-severity and 12 high-severity. These span every release line — what matters is whether the version you run is affected.
Does GitLab have any actively-exploited vulnerabilities?
Yes — 1 GitLab CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild (1 linked to ransomware). Patch it as a priority.
What is the most severe GitLab vulnerability?
Among tracked issues, CVE-2021-22205 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Code injection weakness.
Is GitLab safe to use?
It depends on the version. The latest supported GitLab release (19.2.1) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: GitLab security status · GitLab end-of-life · actively-exploited CVEs. Always verify against GitLab's advisories — see our disclaimer.