CVE-2023-2190

Public Exploit
Authorization Bypass Through User-Controlled Key in GitLab

Description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.10 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1. It may be possible for users to view new commits to private projects in a fork created while the project was public.

Remediation

Solution:

  • Upgrade to versions 16.1.1, 16.0.6, 15.11.10 or above.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.10%
Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/408137 issue tracking broken link vendor advisory
https://hackerone.com/reports/1944500 third party advisory technical description exploit

Frequently Asked Questions

What is the severity of CVE-2023-2190?
CVE-2023-2190 has been scored as a medium severity vulnerability.
How to fix CVE-2023-2190?
To fix CVE-2023-2190: Upgrade to versions 16.1.1, 16.0.6, 15.11.10 or above.
Is CVE-2023-2190 being actively exploited in the wild?
It is possible that CVE-2023-2190 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-2190?
CVE-2023-2190 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.