Skip to main content
VulnerabilityPublished Updated

CVE-2025-9486: GitLab · Incorrect Privilege Assignment

Affects gitlabSource GCVE Database

0
Compare

Not known to be exploited · fixed in 19.2.2 : update gitlab when convenient.

Data as of 15 Nov 2026, 20:25 UTC

Severity
Low

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.2.2, 19.1.4, 19.0.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade gitlab to 19.2.2, 19.1.4 or 19.0.6.

Affected software

ProductAffectedFixed in
Bitnamigitlabpkg:bitnami/gitlabOther threatsAffected
  • >=15.6.0 <19.0.6
  • >=19.1.0 <19.1.4
  • >=19.2.0 <19.2.2
Fixed in
  • 19.0.6
  • 19.1.4
  • 19.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released in GitLab EE versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab instances to these or later versions to remediate the vulnerability.

Description

GitLab Enterprise Edition versions from 15.6 up to but not including 19.0.6, 19.1 up to 19.1.4, and 19.2 up to 19.2.2 contain an incorrect privilege assignment vulnerability. This flaw could allow a user with a pending membership status to receive permissions granted by a custom role, due to the system not properly accounting for membership state. The issue has been remediated in versions 19.0.6, 19.1.4, and 19.2.2 and later.

References

Community reviews

Loading reviews…