CVE-2026-6976 Authorization Bypass Through User-Controlled Key in GitLab

Low 3.7 Published Updated

Authenticated developers can hide changes from merge request diff views due to improper file name handling, bypassing intended visibility controls.

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-6976?

CVE-2026-6976 is a low-severity missing authorization vulnerability in Gitlab Gitlab, published on 11 Jun 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 CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to hide changes from merge request diff views due to improper input handling of file names.

Weakness: CWE-639

Which versions are affected by CVE-2026-6976?

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

PackageAffectedFixed in
gitlab BitnamiFrom 15.9.018.10.8, 18.11.5, 19.0.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-6976?

Upgrade gitlab to a fixed version for your release line: 18.10.8, 18.11.5 or 19.0.2.

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

Is CVE-2026-6976 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-6976, GHSA-7mq5-3vcf-v96v, MINI-28wh-gc22-m4gj, MINI-3h29-mmrq-87ph, MINI-52w4-m36q-4cc7, MINI-5q6h-77rf-5rwr and 41 more.

Is CVE-2026-6976 in your software?

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

Check your SBOMs for free