NVD / CVE Program· CNA GitLab

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

LowCVSS 3.7 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 14/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: GitLab GitLab 18.10.8, 18.11.5, 19.0.2.

Low priority for now. Upgrade to GitLab GitLab 18.10.8, 18.11.5, 19.0.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Broken access control (IDOR)

Published: Jun 11, 2026
Updated: Jun 17, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 14 / 40 · 3.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitLab: 3.7; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gitlab	gitlab	cpe:2.3:a:gitlab:gitlab

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

GitLab GitLab
- 15.9 and later · before 18.10.8affected · semver
- 18.11 and later · before 18.11.5affected · semver
- 19.0 and later · before 19.0.2affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gitlab gitlab15.9.0 and later · before 18.10.8
gitlab gitlab18.11.0 and later · before 18.11.5
gitlab gitlab19.0.0 and later · before 19.0.2

Same product

gitlab: all records

Other highest-scoring records for the same primary product.

CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
100Now
CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
99Now
CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
97Now

Published before and after this one in the same product

← EarlierCVE-2026-6269Jun 11, 2026 · Incorrect Authorization in GitLab
21Monitor
← EarlierCVE-2026-6277Jun 11, 2026 · Incorrect Authorization in GitLab
17Monitor
Later →CVE-2026-7250Jun 11, 2026 · Allocation of Resources Without Limits or Throttling in GitLab
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
GitLab GitLab	18.10.8	Vendor (CNA)
GitLab GitLab	18.11.5	Vendor (CNA)
GitLab GitLab	19.0.2	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

xorzfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1922862 days apartAuthorization Bypass Through User-Controlled Key in GitLab
34Monitor
CVE-2026-486815 days apartAuthorization Bypass Through User-Controlled Key in GitLab
32Monitor
CVE-2026-13319133 days apartAuthorization Bypass Through User-Controlled Key in GitLab
26Monitor
CVE-2025-8770302 days apartAuthorization Bypass Through User-Controlled Key in GitLab
26Monitor
CVE-2026-530914 days apartAuthorization Bypass Through User-Controlled Key in GitLab
21Monitor
CVE-2026-439864 days apartAuthorization Bypass Through User-Controlled Key in GitLab
21Monitor

Bug bounty scope

GitLabHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: Required
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

about.gitlab.com/releases/2026/06/10/patch-release-gitlab-19-0-2-released/

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records