GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under… (CVE-2026-15423)
GitLab CE/EE versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 contain an authorization vulnerability. This flaw could allow an authenticated user with developer-role permissions to execute CI/CD pipelines on protected branches without having the required push permissions. The issue arises from improper authorization in pipeline reference validation. GitLab has remediated this vulnerability in the specified fixed versions.
AI Analysis
Technical Summary
CVE-2026-15423 is an authorization bypass vulnerability in GitLab Community and Enterprise Editions affecting versions from 19.0 prior to 19.0.6, 19.1 prior to 19.1.4, and 19.2 prior to 19.2.2. Under certain conditions, an authenticated user with developer-role permissions could execute CI/CD pipelines on protected branches without possessing the necessary push permissions. The root cause is improper authorization checks during pipeline reference validation. This vulnerability is classified under CWE-863 (Incorrect Authorization).
Potential Impact
An attacker with developer-level access could bypass branch protection controls to run CI/CD pipelines on protected branches, potentially leading to unauthorized code execution or changes in the CI/CD process. The CVSS v3.1 score is 8.5 (High), reflecting network attack vector, low attack complexity, privileges required at the developer level, no user interaction, scope change, low confidentiality impact, high integrity impact, and no availability impact.
Mitigation Recommendations
GitLab has officially remediated this vulnerability in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade to at least these versions to mitigate the issue. Since this is an on-premises product, patching is required by the user. No known exploits are reported in the wild at this time.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under… (CVE-2026-15423)
Description
GitLab CE/EE versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 contain an authorization vulnerability. This flaw could allow an authenticated user with developer-role permissions to execute CI/CD pipelines on protected branches without having the required push permissions. The issue arises from improper authorization in pipeline reference validation. GitLab has remediated this vulnerability in the specified fixed versions.
CVSS v3.1
Score 8.5high
Affected software
pkg:github/gitlab-org/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-15423 is an authorization bypass vulnerability in GitLab Community and Enterprise Editions affecting versions from 19.0 prior to 19.0.6, 19.1 prior to 19.1.4, and 19.2 prior to 19.2.2. Under certain conditions, an authenticated user with developer-role permissions could execute CI/CD pipelines on protected branches without possessing the necessary push permissions. The root cause is improper authorization checks during pipeline reference validation. This vulnerability is classified under CWE-863 (Incorrect Authorization).
Potential Impact
An attacker with developer-level access could bypass branch protection controls to run CI/CD pipelines on protected branches, potentially leading to unauthorized code execution or changes in the CI/CD process. The CVSS v3.1 score is 8.5 (High), reflecting network attack vector, low attack complexity, privileges required at the developer level, no user interaction, scope change, low confidentiality impact, high integrity impact, and no availability impact.
Mitigation Recommendations
GitLab has officially remediated this vulnerability in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade to at least these versions to mitigate the issue. Since this is an on-premises product, patching is required by the user. No known exploits are reported in the wild at this time.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wf8r-f3x5-5p4r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-15423"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a7cd3e4bf8831d539180181
Added to database: 08/12/2026, 20:13:24 UTC
Last enriched: 08/12/2026, 20:56:44 UTC
Last updated: 08/12/2026, 22:01:19 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.