What is the CVSS score of CVE-2026-15831?

CVE-2026-15831 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:N/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2026-15831?

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

GitLab EE CVE-2026-15831

EUVD-2026-50477 MEDIUM

Generation of Incorrect Security Tokens (CWE-1270)

2026-07-29 GitLab

GHSA-w973-7qcg-m257

Gitlab Authentication Bypass

4.3

CVSS 3.1 · Vendor: GitLab

Severity by source

Vendor (GitLab) PRIMARY

4.3 MEDIUM

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

vuln.today AI

4.3 MEDIUM

Aligns with vendor vector; network-accessible with low privileges, integrity-only impact reflecting policy bypass scope, no confidentiality or availability consequence.

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

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 29, 2026 - 20:02 vuln.today

Patch available

Jul 29, 2026 - 20:02 EUVD

CVE Published

Jul 29, 2026 - 19:00 cve.org

MEDIUM 4.3

DescriptionCVE.org

GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation.

AnalysisAI

Improper authorization enforcement during token generation in GitLab Enterprise Edition allows an authenticated low-privilege user to bypass administrator-configured tool governance policies. Affected are all GitLab EE installations running 19.1 before 19.1.3 and 19.2 before 19.2.1. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV; however, the network-accessible, low-privilege attack vector makes this a realistic insider threat in enterprises relying on GitLab EE's governance controls.

Technical ContextAI

GitLab Enterprise Edition implements tool governance policies that allow administrators to define which development or AI-assisted tools specific user roles may access. CWE-1270 (Generation of Incorrect Security Tokens) identifies the root cause: during the token issuance flow, the authorization logic that should enforce governance policy constraints is not correctly applied, potentially resulting in a token that grants broader access than policy permits. The vulnerability is scoped to the EE product tier - features such as tool governance are EE-only - and affects the token generation subsystem specifically. The CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* covers the GitLab application; the EE qualifier is established by the advisory text rather than CPE disambiguation.

RemediationAI

Upgrade GitLab EE to version 19.1.3 (for 19.1.x deployments) or 19.2.1 (for 19.2.x deployments) as the primary fix; both are confirmed by the vendor patch release at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/. If immediate upgrade is not possible, consider restricting token generation to trusted roles via GitLab's role-based access controls, reducing the set of accounts that can initiate token creation. Audit recently issued tokens for scope anomalies against current governance policy as a detection measure. Note that tightening role permissions as a compensating control may affect legitimate workflows - coordinate with development teams before implementing access restrictions.