Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Incorrect Privilege Assignment in GitLab (CVE-2025-9486)

0
Low
Published: 08/18/2026 (08/18/2026, 10:27:35 UTC)
Source: GCVE Database
Product: gitlab

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.

Affected software

Bitnamimore threats →ghsa
gitlab
pkg:bitnami/gitlab
Affected versions
>=15.6.0 <19.0.6>=19.1.0 <19.1.4>=19.2.0 <19.2.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/18/2026, 13:42:50 UTC

Technical Analysis

CVE-2025-9486 is a vulnerability in GitLab Enterprise Edition where under certain conditions, users with pending membership status could improperly receive permissions associated with custom roles. This occurs because the privilege assignment mechanism did not correctly consider the membership state, leading to incorrect privilege grants. The vulnerability affects GitLab EE versions >=15.6.0 <19.0.6, >=19.1.0 <19.1.4, and >=19.2.0 <19.2.2. The issue has been fixed in versions 19.0.6, 19.1.4, and 19.2.2.

Potential Impact

Users with pending membership could gain permissions they should not have, potentially allowing unauthorized access or actions within GitLab projects or groups. The severity is rated low, indicating limited impact or exploitability. There are no known exploits in the wild.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BIT-gitlab-2025-9486
Osv Schema Version
1.6.2
Aliases
["CVE-2025-9486"]
Ecosystems
["Bitnami"]
Database Specific Severity
Low
Cvss Version
null

Threat ID: 6a8460a2c6e8be033245a887

Added to database: 08/18/2026, 13:39:46 UTC

Last enriched: 08/18/2026, 13:42:50 UTC

Last updated: 08/18/2026, 13:42:50 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses