GitLab · GitLab · published 2026-08-27

CVE-2026-4398Authorization Bypass Through User-Controlled Key in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-4398 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% of all CVEs. This GitLab vulnerability: CVSS 5.4 (v3.1). Fixed upstream in GitLab 19.3.1, 19.2.5, 19.1.7. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.3.1, 19.2.5, 19.1.7.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 19.3.1, 19.2.5, 19.1.7

    Upgrade to 19.3.119.2.519.1.7

    Why: Vendor security release for server software (most severe: CVE-2026-18252).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (16th pct)FIRST EPSS v2026.06.15
CVSS base score5.4 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 EE affecting all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.

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 →