Description
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
Score: 8.2 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This vulnerability permits an authenticated user to trigger Duo AI workflow runners on behalf of another user due to faulty user identity resolution when initiating the workflow. The result is that the workflow executes with the target user's privileges, effectively allowing the attacker to execute arbitrary actions under that user’s identity.

Affected Systems

GitLab Enterprise Edition is affected. Versions from 18.8 prior to 18.10.7, from 18.11 prior to 18.11.4, and from 19.0 prior to 19.0.1 are vulnerable; all later releases contain the fix.

Risk and Exploitability

The CVSS score of 8.2 indicates moderate-to-high severity. EPSS data is unavailable, so the current exploitation probability is unknown, and the vulnerability is not listed in CISA KEV. The attack requires a legitimate GitLab account; once authenticated, the user can invoke a Duo AI workflow that the system mistakenly runs under another user’s identity.

Generated by OpenCVE AI on May 27, 2026 at 19:11 UTC.

Remediation

Vendor Solution

Upgrade to versions 18.10.7, 18.11.4, 19.0.1 or above.


OpenCVE Recommended Actions

  • Upgrade GitLab Enterprise Edition to version 18.10.7, 18.11.4, 19.0.1, or later.
  • Limit Duo AI workflow execution to users who have explicit permission to trigger runs if an immediate upgrade is not possible.
  • Examine workflow logs for abnormal activity after applying the patch.

Generated by OpenCVE AI on May 27, 2026 at 19:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 27 May 2026 21:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:gitlab:gitlab:19.0.0:*:*:*:enterprise:*:*:*

Wed, 27 May 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 27 May 2026 18:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Authorization Bypass Through User-Controlled Key in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-639
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-05-28T03:55:58.116Z

Reserved: 2026-03-25T20:33:35.149Z

Link: CVE-2026-4868

cve-icon Vulnrichment

Updated: 2026-05-27T18:58:30.421Z

cve-icon NVD

Status : Analyzed

Published: 2026-05-27T19:16:24.317

Modified: 2026-05-27T20:47:47.137

Link: CVE-2026-4868

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-28T04:45:07Z

Weaknesses