CVE-2026-103549 Incorrect Authorization in GitLab

Low 2.7 Published Updated

Authenticated maintainers can improperly delete protected package registry metadata due to incorrect authorization checks in GitLab.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-103549?

CVE-2026-103549 is a low-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official 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.

Weakness: CWE-863

Which versions are affected by CVE-2026-103549?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 17.6.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-103549?

Upgrade gitlab to a fixed version for your release line: 19.2.8, 19.3.5 or 19.4.2.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-103549 being exploited?

There is no known exploitation of CVE-2026-103549 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-103549, GHSA-mqc6-5cm6-j5mh, MINI-2f97-qr3j-8g7g, MINI-2mq4-r9p5-4938, MINI-329m-wvp4-7f5m, MINI-4q3f-vwpm-w68p and 48 more.

Is CVE-2026-103549 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free