Authorization Bypass Through User-Controlled Key in GitLab

Affected versions

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

• gitlab gitlab18.3.0 and later · before 19.1.7
• gitlab gitlab19.2.0 and later · before 19.2.5
• gitlab gitlab19.3.0

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

  • 18.3 and later · before 19.1.7affected · semver
  • 19.2 and later · before 19.2.5affected · semver
  • 19.3 and later · before 19.3.1affected · semver

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
  97Now
• CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
  97Now
• CVE-2021-22175When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versionsKEV
  85Now
• CVE-2021-39935An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.5 before 14.3.6, all versions starting from 14.4 beforeKEV
  71This week
• CVE-2022-2992A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated us
  65This week

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

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

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

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.