tag: Patch · 3 items
- 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)
- Platform/SRE — Plan: Critical patch releases in GitLab warrant upgrading if you self-host; review CVE details in the release notes and schedule the upgrade to the applicable branch (19.4.2, 19.3.4, or 19.2.8) this sprint. No exploitation confirmed in signals, so Act ceiling is not reached.
- CI/CD — Plan: If GitLab CI is your pipeline platform and you run a self-managed instance, plan an upgrade to the patched version matching your branch; critical patches can affect runner availability and API stability. No hard deadline or active exploitation in signals.
- Leader — Skip
- Platform/SRE — Plan: CVE-2026-14978 (Unicode normalization in go-slug) can cause files to leak into HCP Terraform/TFE runs despite .terraformignore rules; not KEV-listed and EPSS 0.00, but worth upgrading Terraform to 1.15.9 in the next maintenance window if you upload sensitive files via remote runs.
- CI/CD — Plan: If pipelines run Terraform remote operations against HCP Terraform or Terraform Enterprise, the .terraformignore bypass in CVE-2026-14978 could leak secrets or config files into run uploads; pin Terraform to 1.15.9 in CI pipeline tooling during the next scheduled update.
- Leader — Skip
- Signals: CVE-2026-14978 — CISA KEV: not listed, EPSS 0.00