ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-4868

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

Published May 27, 2026 · catalog updated Oct 14, 2026 · GitLab GitLab

Check if you run it

No confirmed exploitation is on record for CVE-2026-4868. EPSS is 0.46%. Act only if a listed version of GitLab GitLab is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.46%
Remediation
Advisory link
Affected products
cpe gitlab/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 identi

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe gitlab/gitlab19.0.0

How to fix CVE-2026-4868

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-4868. EPSS is 0.46%. Act only if a listed version of GitLab GitLab is installed.

Which versions are affected?

Compare what you have installed with 19.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-639: Authorization Bypass Through User-Controlled Key. EPSS 0.46%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 27, 2026 · NIST NVD

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-4868

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-4868

    30-day exploitation probability 0.5%

    first.org
  • GitLab Security ReleasesVendor advisoryCVE-2026-4868

    On May 27, 2026, we released versions 19.0.1, 18.11.4, 18.10.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these

    docs.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-4868

    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 identi

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.