CVE-2026-7487 Access Control Check Implemented After Asset is Accessed in GitLab

Low 3.5 Published 26 Aug 2026 Updated 26 Aug 2026

Authenticated reporters can bypass authorization checks to reset merge request approval rules in GitLab Enterprise Edition.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: Available

What is CVE-2026-7487?

CVE-2026-7487 is a low-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.

Weakness: CWE-1280

Which versions are affected by CVE-2026-7487?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `13.1.0`	`19.1.7, 19.2.5, 19.3.1`

Products include Gitlab Gitlab.

How do I fix CVE-2026-7487?

Upgrade gitlab to a fixed version for your release line: 19.1.7, 19.2.5 or 19.3.1.

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

Is CVE-2026-7487 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-7487, GHSA-r8m7-3v38-qjrm, MINI-98h2-9j6v-57gq, MINI-pv8f-xjh8-456x, MINI-xh66-qv96-xxr9.