Plan
active
GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6 and earlier branches
- Platform/SRE — Plan: If you self-host GitLab, schedule an upgrade to the relevant patched branch (19.5.1, 19.4.3, 19.3.6, etc.) this sprint; GitLab’s ‘Critical’ designation signals high-severity CVEs, but no KEV listing or active exploitation is confirmed in the signals, so this is urgent planned work rather than a drop-everything hotfix.
- CI/CD — Plan: Teams running self-hosted GitLab CI should upgrade to the appropriate patched version for their minor branch; a critical security fix in the CI/CD platform itself is a supply-chain risk that warrants scheduling an upgrade this sprint, even without confirmed exploitation.
- Leader — Skip
- Signals: major release (19.0)
This entry was curated and judged by AI (Claude) with automated enrichment
(CISA KEV / EPSS / public PoC). Verify against the original source before
acting. Found a bad verdict?
Report it —
confirmed errors go to the corrections log.