CVE-2026-103549
Received Received - Intake

Authenticated User Package Registry Metadata Removal in GitLab CE/EE

Publication date: 2026-10-13

Last updated on: 2026-10-13

Assigner: GitLab Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-13
Last Modified
2026-10-13
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
CVE-2026-103549
EUVD
EUVD-2026-98209

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
GitLab GitLab 17.6
GitLab GitLab 19.3
GitLab GitLab 19.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in GitLab CE/EE allows an authenticated user with maintainer permissions to remove certain package registry metadata that should be restricted to higher roles. This happens due to improper authorization checks in versions before 19.2.8, 19.3.5, and 19.4.2.

Detection Guidance

This vulnerability requires checking GitLab instances for unauthorized removal of package registry metadata by maintainer-role users. Review audit logs for package registry changes and verify package protection rules are enforced. No specific commands are provided in the context.

Impact Analysis

An attacker with maintainer access could bypass package protection rules and remove critical metadata, potentially disrupting package integrity or causing unauthorized changes to protected packages.

Compliance Impact

This vulnerability could potentially impact compliance with standards like GDPR and HIPAA by allowing unauthorized users to modify package registry metadata, which may lead to data integrity issues or unauthorized access to sensitive data. However, the specific impact depends on how the affected GitLab instance is used within a compliance framework.

Mitigation Strategies

Upgrade GitLab to a patched version (19.2.8, 19.3.5, or 19.4.2 or later) to address the improper authorization checks in package registry metadata removal.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-103549. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart