Products · DevOps · exposure: server

GitLab

https://about.gitlab.com/releases/categories/releases/

Share this

Security releases 35

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.6.1, 19.5.8, 19.4.10

    Upgrade to 19.6.119.5.819.4.10

    Why: Vendor security release for server software (most severe: CVE-2026-132825).

  2. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.5.6, 19.4.8, 19.3.9

    Upgrade to 19.5.619.4.819.3.9

    Why: Vendor security release for server software (most severe: CVE-2026-105739).

  3. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.5.5, 19.4.7

    Upgrade to 19.5.519.4.7

    Why: Vendor security release for server software; CVE details not linked yet.

  4. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.5.4, 19.4.6, 19.3.8

    Upgrade to 19.5.419.4.619.3.8

    Why: Public proof-of-concept exists (SSVC exploitation: poc).

  5. This monthSecurity release

    DevOpsGitLab

    GitLab security fixes: 1 CVE

    Upgrade to 19.5.319.4.519.3.719.2.1019.1.1019.0.1118.11.14

    Why: Vendor security release for server software (most severe: CVE-2026-111943).

  6. This monthSecurity release

    DevOpsGitLab

    GitLab security fixes: 12 CVEs

    Upgrade to 19.5.119.4.319.3.619.2.919.1.919.0.1018.11.13

    Why: CVE-2026-110264: EPSS 1.3% with high severity (CVSS 10).

  7. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.4.2, 19.3.5, 19.2.8

    Upgrade to 19.4.219.3.519.2.8

    Why: CVE-2026-97229: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

  8. This weekSecurity release

    DevOpsGitLab

    GitLab security releases: 19.4.1, 19.3.2, 19.2.4

    Upgrade to 19.4.119.3.219.2.4

    Why: EPSS 17% chance of exploitation in 30 days, with critical impact.

  9. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.4.1, 19.3.3, 19.2.7, 19.0.9, 18.11.12

    Upgrade to 19.4.119.3.319.2.719.0.918.11.12

    Why: CVE-2026-85706: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

  10. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.3.2, 19.2.6, 19.1.8

    Upgrade to 19.3.219.2.619.1.8

    Why: CVE-2026-85706: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

  11. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.3.1, 19.2.5, 19.1.7

    Upgrade to 19.3.119.2.519.1.7

    Why: Vendor security release for server software (most severe: CVE-2026-18252).

  12. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.2.4, 19.1.6, 19.0.8, 18.11.11

    Upgrade to 19.2.419.1.619.0.818.11.11

    Why: CVE-2026-19478: EPSS 2.2% with high severity (CVSS 9.4).

  13. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.2.2, 19.1.4, 19.0.6

    Upgrade to 19.2.219.1.419.0.6

    Why: CVE-2026-4879: Public proof-of-concept exists (SSVC exploitation: poc).

  14. This monthSecurity release

    DevOpsGitLab

    GitLab security release: 18.11.9

    Upgrade to 18.11.9

    Why: Vendor security release for server software; CVE details not linked yet.

  15. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.2.1, 19.1.3, 19.0.5

    Upgrade to 19.2.119.1.319.0.5

    Why: CVE-2026-6336: Public proof-of-concept exists (SSVC exploitation: poc).

  16. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.1.2, 19.0.4, 18.11.7

    Upgrade to 19.1.219.0.418.11.7

    Why: Vendor security release for server software (most severe: CVE-2026-6896).

  17. This monthSecurity release

    DevOpsGitLab

    GitLab security release: 18.8.11

    Upgrade to 18.8.11

    Why: Vendor security release for server software; CVE details not linked yet.

  18. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.1.1, 19.0.3, 18.11.6

    Upgrade to 19.1.119.0.318.11.6

    Why: Vendor security release for server software (most severe: CVE-2026-10086).

  19. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.0.2, 18.11.5, 18.10.8

    Upgrade to 19.0.218.11.518.10.8

    Why: Vendor security release for server software (most severe: CVE-2026-10087).

  20. This monthSecurity release

    DevOpsGitLab

    GitLab security fixes: 7 CVEs

    Upgrade to 19.0.118.11.418.10.718.9.818.8.1018.7.718.6.818.5.7

    Why: CVE-2026-1402: Public proof-of-concept exists (SSVC exploitation: poc).

  21. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.11.3, 18.10.6, 18.9.7

    Upgrade to 18.11.318.10.618.9.7

    Why: Vendor security release for server software (most severe: CVE-2026-6073).

  22. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.11.2, 18.10.5

    Upgrade to 18.11.218.10.5

    Why: Vendor security release for server software; CVE details not linked yet.

  23. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.11.1, 18.10.4, 18.9.6

    Upgrade to 18.11.118.10.418.9.6

    Why: CVE-2025-0186: Public proof-of-concept exists (SSVC exploitation: poc).

  24. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.10.3, 18.9.5, 18.8.9

    Upgrade to 18.10.318.9.518.8.9

    Why: CVE-2026-1092: Public proof-of-concept exists (SSVC exploitation: poc).

  25. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.10.1, 18.9.3, 18.8.7

    Upgrade to 18.10.118.9.318.8.7

    Why: CVE-2025-13078: Public proof-of-concept exists (SSVC exploitation: poc).

  26. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.9.2, 18.8.6, 18.7.6

    Upgrade to 18.9.218.8.618.7.6

    Why: CVE-2025-14513: Public proof-of-concept exists (SSVC exploitation: poc).

  27. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.9.1, 18.8.5, 18.7.5

    Upgrade to 18.9.118.8.518.7.5

    Why: CVE-2026-1388: Public proof-of-concept exists (SSVC exploitation: poc).

  28. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.8.4, 18.7.4, 18.6.6

    Upgrade to 18.8.418.7.418.6.6

    Why: CVE-2026-1387: Public proof-of-concept exists (SSVC exploitation: poc).

  29. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.8.1, 18.7.1, 18.6.2

    Upgrade to 18.8.118.7.118.6.2

    Why: Vendor security release for server software (most severe: CVE-2026-1868).

  30. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.8.3, 18.7.3, 18.6.5

    Upgrade to 18.8.318.7.318.6.5

    Why: Vendor security release for server software; CVE details not linked yet.

  31. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.8.2, 18.7.2, 18.6.4

    Upgrade to 18.8.218.7.218.6.4

    Why: CVE-2026-0723: EPSS 1.0% with high severity (CVSS 7.4).

  32. This monthSecurity release

    DevOpsGitLab

    GitLab security release: 18.8.1

    Upgrade to 18.8.1

    Why: Vendor security release for server software; CVE details not linked yet.

  33. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.7.1, 18.6.3, 18.5.5

    Upgrade to 18.7.118.6.318.5.5

    Why: CVE-2025-64720: Public proof-of-concept exists (SSVC exploitation: poc).

  34. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.6.2, 18.5.4, 18.4.6

    Upgrade to 18.6.218.5.418.4.6

    Why: Vendor security release for server software (most severe: CVE-2025-12716).

  35. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.6.1, 18.5.3, 18.4.5

    Upgrade to 18.6.118.5.318.4.5

    Why: Vendor security release for server software (most severe: CVE-2024-9183).

Known exploited (CISA KEV) 6

  1. Patch todayExploited (KEV)CISA due 2026-11-01

    DevOpsGitLab

    Integer Overflow or WraparoundCVE-2026-97229

    Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

  2. Patch todayExploited (KEV)CISA due 2026-09-14

    DevOpsGitLab

    Path TraversalCVE-2026-85706

    Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

  3. Patch todayExploited (KEV)CISA due 2026-03-11

    DevOpsGitLab

    Server-Side Request Forgery (SSRF)CVE-2021-22175

    Why: Known exploited server software, total technical impact.

  4. This weekExploited (KEV)CISA due 2026-02-24

    DevOpsGitLab

    Server-Side Request Forgery (SSRF)CVE-2021-39935

    Why: Known exploited in the wild.

  5. Patch todayExploited (KEV)CISA due 2024-05-22

    DevOpsGitLab

    Community and Enterprise Editions Improper Access ControlCVE-2023-7028

    Why: Known exploited server software, exploitation is automatable, total technical impact.

  6. Patch todayExploited (KEV)CISA due 2021-11-17

    DevOpsGitLab

    Remote Code ExecutionCVE-2021-22205

    Why: Known exploited and used in ransomware campaigns.

Also on today's list

See today's list → · Coming up →