What is the CVSS score of EUVD-2026-20797?

EUVD-2026-20797 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for EUVD-2026-20797?

Yes, a patch is available for EUVD-2026-20797. Update the affected software to the latest version immediately.

Gitlab EUVD-2026-20797

| CVE-2026-2104 MEDIUM

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-04-08 cve@gitlab.com

GHSA-4759-m874-gwp3

Authentication Bypass Gitlab

4.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

18.10.3,18.8.9,18.9.5

EUVD ID Assigned

Apr 08, 2026 - 23:24 euvd

EUVD-2026-20797

Analysis Generated

Apr 08, 2026 - 23:24 vuln.today

CVE Published

Apr 08, 2026 - 23:16 nvd

MEDIUM 4.3

DescriptionCVE.org

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to access confidential issues assigned to other users via CSV export due to insufficient authorization checks.

AnalysisAI

GitLab CE/EE versions 18.2-18.10.2 allow authenticated users to export confidential issues assigned to other users via CSV export due to missing authorization validation. The vulnerability affects approximately three release branches with a moderate CVSS score of 4.3, limited by the requirement for prior authentication and lack of integrity impact, but represents a direct confidentiality breach in multi-tenant environments where issue classification is a security boundary.

Technical ContextAI

GitLab's CSV export functionality for issues fails to enforce row-level authorization checks that verify whether the authenticated user has permission to view specific issues before including them in the export output. The root cause is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), meaning the application relies on user-supplied parameters or session context without validating resource-level access policies. The vulnerability manifests in the CE (Community Edition) and EE (Enterprise Edition) products across versions 18.2.x, 18.9.x, and 18.10.x prior to their respective patch releases. The issue is specific to the CSV export mechanism and does not affect other issue viewing interfaces, suggesting a secondary code path was overlooked during authorization refactoring.

RemediationAI

Upgrade GitLab to version 18.8.9 or later if on the 18.8 branch, 18.9.5 or later if on the 18.9 branch, or 18.10.3 or later if on the 18.10 branch. These patched versions restore authorization checks to the CSV export functionality, ensuring authenticated users cannot access confidential issues outside their visible scope. Consult https://about.gitlab.com/releases/2026/04/08/patch-release-gitlab-18-10-3-released/ for detailed upgrade instructions and release notes. Workarounds are not documented in the available references; if immediate patching is not feasible, restrict CSV export permissions via role-based access controls or monitor export logs for unauthorized access patterns.