dbcve.org
GitLabApplication

CVE-2026-4868

HIGH · 8.2 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 18.10.7 / 18.11.4 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This GitLab EE vulnerability allows an authenticated user to impersonate another user when triggering Duo AI workflow runners due to improper user identity resolution. The issue stems from the workflow runner not correctly validating the authenticated user's identity before executing workflows, enabling privilege escalation through identity confusion.

MitigationUpgrade GitLab to version 18.10.7, 18.11.4, or 19.0.1 or later. Review Duo AI workflow execution logs to identify any unauthorized workflow runs that may have occurred under different user identities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 18.8.0, < 18.10.7>= 18.11.0, < 18.11.4= 19.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run 'gitlab-rake gitlab:version' or check via the GitLab UI at Help > Version, or query the API at /api/v4/version
    Affected if The installed version falls within 18.8.0 to 18.10.6, 18.11.0 to 18.11.3, or exactly 19.0.0
  2. Verify Duo AI workflow runners are enabled
    Check GitLab settings under CI/CD > Runners or the Duo AI settings area for any configured workflow runners
    Affected if Duo AI workflow runners are actively configured or have been used in the environment
  3. Review workflow execution audit logs for identity anomalies
    Access GitLab audit logs (Admin Area > Audit Events or via the audit events API) and filter for Duo workflow execution events, looking for cases where the triggering user differs from the effective user
    Affected if Audit logs show workflow executions where the authenticated user identity does not match the expected user context, or unexpected user impersonation patterns exist

A GitLab instance is affected if it runs an affected version (18.8.0-18.10.6, 18.11.0-18.11.3, or 19.0.0) AND has Duo AI workflow runners enabled, with potential evidence in audit logs of identity confusion during workflow execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.10.7 / 18.11.4 or later
Fixed in 18.10.718.11.4
Interim mitigation

Upgrade GitLab to version 18.10.7, 18.11.4, or 19.0.1 or later. Review Duo AI workflow execution logs to identify any unauthorized workflow runs that may have occurred under different user identities.

Recommended fix High confidence

19.0.1 (or latest 19.x stable release)

  1. Identify your current GitLab version by checking the GitLab administration interface or running `gitlab-rake gitlab:version`
  2. Determine which release branch you are on (18.8-18.10, 18.11, or 19.0)
  3. Plan upgrade based on your current version: if on 18.8.x-18.9.x, upgrade to 18.10.7 or later; if on 18.11.x, upgrade to 18.11.4 or later; if on 19.0.0, upgrade to 19.0.1 or later
  4. Follow standard GitLab upgrade procedures for your installation method (omnibus, source, etc.)
  5. After upgrade, verify the GitLab version matches a fixed release
Caveat Review GitLab 19.0 release notes for any breaking changes before upgrading, as major version upgrades may include deprecations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4868 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data