# CVE-2025-9486: Incorrect Privilege Assignment in GitLab > A user with pending membership could incorrectly receive permissions from a custom role due to flawed privilege assignment logic in GitLab EE. - **Severity:** Low 3.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Aug 2026 - **Updated:** 13 Aug 2026 - **Also known as:** BIT-gitlab-2025-9486, GHSA-j94w-j9cr-q9pj, MINI-7328-vfhw-w2c3, MINI-gv4v-fjjv-hcg9 ## What is CVE-2025-9486? CVE-2025-9486 is a low-severity vulnerability in Gitlab Gitlab, published on 12 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official 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. Weakness: CWE-266 (Incorrect Privilege Assignment) ## Which versions are affected by CVE-2025-9486? 1 open source package ship an affected version, including gitlab. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gitlab` | Bitnami | From 15.6.0 | 19.0.6, 19.1.4, 19.2.2 | Products: Gitlab Gitlab. ## How do I fix CVE-2025-9486? Upgrade gitlab to a fixed version for your release line: 19.0.6, 19.1.4 or 19.2.2. ## Is CVE-2025-9486 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9486 exists. ## Other vulnerabilities in Gitlab Gitlab - [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild) - [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild) - [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-9486 and fix it if it is affected. What it is: CVE-2025-9486 is a low-severity vulnerability in Gitlab Gitlab, published on 12 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9486 exists. Affected packages and fixed versions: - gitlab (Bitnami): affected from 15.6.0; fixed in 19.0.6, 19.1.4, 19.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-9486/ (Markdown: https://insights.sbomify.com/CVE-2025-9486/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9486 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9486 - OSV: https://osv.dev/vulnerability/CVE-2025-9486 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-9486/ Summaries are generated and may contain mistakes; the official description above is the record.