CVE-2026-16275 Incorrect Authorization in GitLab

Medium 5.3 Published Updated

An unauthenticated attacker can read confidential notes on public projects due to incorrect authorization checks in GitLab.

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

What is CVE-2026-16275?

CVE-2026-16275 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.4 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 unauthenticated user to read confidential notes on public projects due to incorrect authorization checks.

Weakness: CWE-863

Which versions are affected by CVE-2026-16275?

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

PackageAffectedFixed in
gitlab BitnamiFrom 17.4.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-16275?

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-16275 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-16275, GHSA-mvmh-ccfp-m833, MINI-2244-9fv4-w567, MINI-2fjm-9hhp-ggvj, MINI-2j3f-ff29-qm8p, MINI-2x7g-mxqh-q826 and 48 more.

Is CVE-2026-16275 in your software?

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

Check your SBOMs for free