GitLab · GitLab · published 2026-10-13

CVE-2026-82632Incorrect Authorization in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-82632 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This GitLab vulnerability: CVSS 3.1 (v3.1). Fixed upstream in GitLab 19.4.2, 19.3.5, 19.2.8. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.4.2, 19.3.5, 19.2.8.

Patch events

  1. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.4.2, 19.3.5, 19.2.8

    Upgrade to 19.4.219.3.519.2.8

    Why: CVE-2026-97229: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (12th pct)FIRST EPSS v2026.06.15
CVSS base score3.1 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA 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 CE/EE affecting all versions from 18.9 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace.

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 →