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.
Published: 2026-08-12
Score: 3.3 Low
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in GitLab Enterprise Edition’s handling of custom role assignments. When a user has a pending membership, GitLab may incorrectly grant that user the permissions associated with a custom role, allowing an attacker who controls or abuses such a pending membership to acquire unauthorized privileges, which is a classic CWE‑266 weakness.

Affected Systems

The issue affects GitLab Enterprise Edition across a broad range of releases: all versions from 15.6 up to but excluding 19.0.6, from 19.1 up to excluding 19.1.4, and from 19.2 up to excluding 19.2.2. Updating to any version 19.0.6, 19.1.4, 19.2.2 or later resolves the problem.

Risk and Exploitability

The CVSS score is 3.3, indicating low overall severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack surface requires an account with a pending association to leverage the custom role; it is therefore limited to users who already have a pending membership within the system. While the risk is low, the potential for unauthorized privilege escalation warrants patching. The vendor recommends upgrading to the stated patched releases to eliminate the flaw.

Generated by OpenCVE AI on August 12, 2026 at 22:40 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.0.6, 19.1.4, 19.2.2 or above.


OpenCVE Recommended Actions

  • Upgrade GitLab Enterprise Edition to at least version 19.0.6, 19.1.4, 19.2.2 or newer releases.
  • Audit existing pending membership accounts to confirm no unauthorized roles were assigned during the vulnerability window.
  • Review and tighten configuration that controls pending membership transitions, removing any unnecessary pending states or restricting role assignments until membership is approved.

Generated by OpenCVE AI on August 12, 2026 at 22:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 12 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
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.
Title Incorrect Privilege Assignment in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-266
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-08-12T19:05:46.417Z

Reserved: 2025-08-26T12:05:02.058Z

Link: CVE-2025-9486

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-12T20:17:33.120

Modified: 2026-08-12T20:17:33.120

Link: CVE-2025-9486

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T00:00:08Z

Weaknesses
  • CWE-266

    Incorrect Privilege Assignment