Policy bypass via unauthorized token generation
Published Jul 29, 2026 · Updated Jul 29, 2026
Incorrect token generation in GitLab EE 19.1 through 19.1.2 and 19.2 through 19.2.0 allows remote authenticated users to bypass tool policies. The Duo Workflows token-generation path fails to enforce administrator-configured tool governance authorization, producing tokens that permit disallowed tool use. Authenticated access and the undisclosed conditions are required; successful exploitation changes which governed tools the account can invoke.
Summary
What happened
Incorrect token generation in GitLab EE 19.1 through 19.1.2 and 19.2 through 19.2.0 allows remote authenticated users to bypass tool policies. The Duo Workflows token-generation path fails to enforce administrator-configured tool governance authorization, producing tokens that permit disallowed tool use. Authenticated access and the undisclosed conditions are required; successful exploitation changes which governed tools the account can invoke.
The record
- CVE
- CVE-2026-15831
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-1270
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=19.1 <19.1.3
- Affected versionversion=19.2 <19.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo