CVE-2026-15831

Analyzed Analyzed - Analysis Complete

GitLab EE Tool Governance Policy Bypass via Token Generation

Publication date: 2026-07-29

Last updated on: 2026-08-03

Assigner: GitLab Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-08-03

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-15831

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 19.1.0 (inc) to 19.1.3 (exc)
gitlab	gitlab	19.2.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-1270	The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab EE allows an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation. It affects versions 19.1 before 19.1.3 and 19.2 before 19.2.1.

Detection Guidance

This vulnerability affects GitLab EE versions before 19.1.3 and 19.2.1. To detect it, check your GitLab EE version using the command: gitlab-rake gitlab:env:info. If your version is below 19.1.3 or 19.2.1, the system is vulnerable.

Impact Analysis

An attacker with access could generate tokens that bypass security policies, potentially allowing unauthorized actions or access to restricted resources within GitLab.

Compliance Impact

The vulnerability allows an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation. This could potentially lead to unauthorized access or misuse of sensitive data, which may impact compliance with standards like GDPR or HIPAA that require strict access controls and audit trails.

Mitigation Strategies

Update GitLab EE to version 19.1.3 or later if using 19.1.x, or to version 19.2.1 or later if using 19.2.x to address the authorization bypass issue.

Hi! I’m here to help you understand CVE-2026-15831. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70