CVE-2026-4868 | Authorization Bypass Through User-Controlled Key in GitLab

GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that, under certain conditions, could have allowed an authenticated user to cause specific Duo AI workflows to run under another user's identity due to improper user identity resolution when triggering Duo AI workflow runners.

Published: 2026-05-27 Last update: 2026-05-27 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4868 is rated Low Risk (39.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.28%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-4868

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.28% +0.27%
2 2026-05-28 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4868

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.8 [email protected]

Weakness enumeration for CVE-2026-4868

GitHub Security Advisory for CVE-2026-4868

GHSA-64q9-48cg-f6vv · Severity: high — GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.10.7, 18...

OS Trackers for CVE-2026-4868

vendor priority summary link
ubuntu medium CVE-2026-4868 medium priority: Ubuntu including 1 source packages (gitlab), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): DNE 4, not-affected 1. https://ubuntu.com/security/CVE-2026-4868

Affected software / configurations for CVE-2026-4868

Vendor Product Version Raw CPE
gitlab gitlab >= 18.8.0, < 18.10.7 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.11.0, < 18.11.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab 19.0.0 cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:enterprise:*:*:*

References for CVE-2026-4868

cvelogic Threat Intelligence