CVE-2026-103549
2.7LowPublished 13 Oct 2026 · NVD status: Analyzed · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- High
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-863
Impact
Authenticated maintainers can bypass package protection rules to delete package registry metadata restricted to higher roles. They need an active account with maintainer privileges to exploit this.
Root cause
Improper authorization checks fail to enforce package protection restrictions against maintainer accounts during metadata deletion.
Affected systems
GitLab CE/EE versions 17.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Fix & remediation
Upgrade GitLab to 19.2.8, 19.3.5, 19.4.2, or later. No interim mitigation is documented; restrict maintainer permissions on sensitive projects until patched.
$ sudo apt-get update && sudo apt-get install --only-upgrade gitlab-eeAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with maintainer-role permissions to remove certain package registry metadata that package protection rules restrict to higher roles, due to improper authorization checks.
References
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/Release NotesVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/work_items/631531Issue Tracking