Summary iPlain-English security verdict for GitLab, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
GitLab currently scores 100/100 — healthy. 1 actively-exploited vulnerability (CISA KEV) affects older releases (e.g. CVE-2021-22205) — staying on the latest supported version keeps you clear of it. The latest supported release is 19.3.1. It's on the latest patch with no significant known issues — keep it current.
Disclosure trend iNew CVEs published for GitLab each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
1 of its known vulnerability is linked to ransomware campaigns (CISA KEV).
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2021-22205 CRITICAL exploited ransomware Code injection EPSS 100% → fixed in 13.10.3 CVE-2026-19478 CRITICAL Code injection EPSS 6% → fixed in 19.2.4Get alerted about GitLab
Be emailed the moment GitLab gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for GitLab — no marketing, no sharing, and we never know what you run. Track your whole stack →
Versions & lifecycle iWhen each release line stops receiving security patches (end-of-life). After EOL there are no more fixes — plan upgrades before these dates.
How long each GitLab release line is supported — and when it sunsets. Select a line for its full report.
Full GitLab end-of-life dates & support timeline →
19.3 latest 19.3.1 Supported until 2026-11-1919.3.1 → 19.2 latest 19.2.5 Supported until 2026-10-1519.2.5 → 19.1 latest 19.1.7 Supported until 2026-09-1719.1.7 → 19.0 latest 19.0.8 End of life ended 2026-08-2019.0.8 → 18.11 latest 18.11.11 End of life ended 2026-07-1618.11.11 → 18.10 latest 18.10.8 End of life ended 2026-06-1818.10.8 → 18.9 latest 18.9.8 End of life ended 2026-05-2118.9.8 → 18.8 latest 18.8.11 End of life ended 2026-04-1618.8.11 → 18.7 latest 18.7.7 End of life ended 2026-03-1918.7.7 → 18.6 latest 18.6.8 End of life ended 2026-02-1918.6.8 → See all upcoming end-of-life dates →Frequently asked
Is GitLab safe and patched?
GitLab currently scores 100/100 — healthy. 1 actively-exploited vulnerability (CISA KEV) affects older releases (e.g. CVE-2021-22205) — staying on the latest supported version keeps you clear of it. The latest supported release is 19.3.1. It's on the latest patch with no significant known issues — keep it current.
What should I do about GitLab now?
Upgrade GitLab to the latest supported release (19.3.1) or later, which clears the actively-exploited issues affecting older versions, then confirm against GitLab's official advisory.
When does GitLab reach end-of-life?
The latest supported GitLab release is 19.3.1. After end-of-life a release no longer receives security patches.
Which versions of GitLab are still receiving security updates?
Supported GitLab release lines (latest 19.3.1): 19.3, 19.2, 19.1. End-of-life releases no longer receive security patches.
Latest security news for GitLab BETA
Attributed third-party reporting linked to GitLab — newest first. We surface and link the source; we don’t assert our own findings. About Emerging →
More across all tracked software on the Emerging feed →
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against GitLab's official advisory before you patch or upgrade — GitLab official site ↗