GitLab · GitLab · published 2026-08-12

CVE-2025-9486Incorrect Privilege Assignment in GitLab

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2025-9486 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 28% of all CVEs. This GitLab vulnerability: CVSS 3.3 (v3.1). Fixed upstream in GitLab 19.2.2, 19.1.4, 19.0.6. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in GitLab 19.2.2, 19.1.4, 19.0.6.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.2.2, 19.1.4, 19.0.6

    Upgrade to 19.2.219.1.419.0.6

    Why: CVE-2026-4879: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (28th pct)FIRST EPSS v2026.06.15
CVSS base score3.3 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →