GitLab: maintainers can delete package registry metadata that protection rules reserve for higher roles

Impact

Improper authorization lets a user with the maintainer role remove package registry metadata that package protection rules were configured to restrict to higher roles. Where a self-hosted GitLab registry is the distribution point for container images or language packages that GPU nodes pull, protection rules are the control that keeps release artifacts from being tampered with by project-level roles; this bypasses part of that control. Integrity only - no confidentiality or availability impact is claimed - and it requires an already-privileged project role, so this is a defence-in-depth regression rather than a path in from outside.

Who can reach it

Authenticated GitLab user holding the maintainer role on the project, over the network. High privilege required; no user interaction.

What to do

Upgrade self-hosted GitLab to 19.2.8, 19.3.5 or 19.4.2 (affected from 17.6) and restart the application. Same patch release as the other GitLab fixes in this cycle, so one upgrade covers them. In the meantime, treat maintainer as effectively able to prune protected package metadata and review registry audit events for unexpected deletions.

References

Related entries

• Jenkins: project naming strategy config lets Overall/Manage holders instantiate admin-only typesCVE-2026-70430 · Jenkins core (project naming strategy configuration)Low
• GitLab EE: insufficient access control lets a limited user modify project CI/CD deployment rollback settingsCVE-2026-9268 · GitLab EE CI/CD deployment rollback settings (access control)Low
• Sunbird Power IQ 9.2.0 API: Error-based SQL injection through an outdated API endpoint with missing input validationCVE-2025-55703 · Sunbird Power IQ 9.2.0 APILow
• Trivy: Terraform filesystem functions read paths above the scan root during misconfig scansCVE-2026-104994 · Trivy (Terraform misconfiguration scanner, filesystem functions)Low
• Lenovo ThinkSystem SR670 V2 (shipped in Manufacturing Mode): SR670 V2 servers built between roughly June 2021 and JulyCVE-2024-23591 · Lenovo ThinkSystem SR670 V2 (shipped in Manufacturing Mode)Low
• Linuxfabrik monitoring plugins: symlink attack on predictable /tmp SQLite caches lets a local user write as rootCVE-2026-53759 · linuxfabrik-lib db_sqlite.py (Monitoring Plugins cache databases in /tmp)Low