GitLab · GitLab · published 2026-09-16

CVE-2026-86341Access Control Check Implemented After Asset is Accessed in GitLab

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-86341 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This GitLab vulnerability: CVSS 4.4 (v3.1). Fixed upstream in GitLab 19.3.2, 19.2.6, 19.1.8. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.3.2, 19.2.6, 19.1.8.

Patch events

  1. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.3.2, 19.2.6, 19.1.8

    Upgrade to 19.3.219.2.619.1.8

    Why: CVE-2026-85706: 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.4% (31th pct)FIRST EPSS v2026.06.15
CVSS base score4.4 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/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 EE affecting all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user with Owner or Maintainer permissions could have silently disabled protected environment deployment approval requirements, allowing unapproved deployments to reach production, due to improper access control checks performed after the protected resource was modified.

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 →