GitLab has remediated an issue in GitLab EE affecting all versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under… (CVE-2026-13113)
A vulnerability in GitLab EE versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an authenticated user to merge code into a protected branch without the required approvals. This occurs due to a race condition in the approval rule processing. The issue has been remediated in the specified fixed versions.
AI Analysis
Technical Summary
CVE-2026-13113 is a race condition vulnerability in GitLab EE affecting multiple version ranges: from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Under certain conditions, an authenticated user could bypass required approval rules and merge code into protected branches without the necessary approvals. This vulnerability relates to improper synchronization in approval rule processing (CWE-367). The flaw has been fixed in GitLab EE versions 19.0.5, 19.1.3, and 19.2.1 and later.
Potential Impact
The vulnerability allows an authenticated user to bypass branch protection mechanisms by merging code into protected branches without the required approvals. This can lead to unauthorized code changes being introduced, impacting the integrity of the codebase. There is no impact on confidentiality or availability reported. No known exploits in the wild have been identified.
Mitigation Recommendations
A fix is available. Users should upgrade to GitLab EE versions 19.0.5, 19.1.3, or 19.2.1 or later to remediate this vulnerability. Applying these official fixes will prevent exploitation of the race condition in approval rule processing.
GitLab has remediated an issue in GitLab EE affecting all versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under… (CVE-2026-13113)
Description
A vulnerability in GitLab EE versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an authenticated user to merge code into a protected branch without the required approvals. This occurs due to a race condition in the approval rule processing. The issue has been remediated in the specified fixed versions.
CVSS v3.1
Score 6.5medium
Affected software
pkg:gem/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-13113 is a race condition vulnerability in GitLab EE affecting multiple version ranges: from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Under certain conditions, an authenticated user could bypass required approval rules and merge code into protected branches without the necessary approvals. This vulnerability relates to improper synchronization in approval rule processing (CWE-367). The flaw has been fixed in GitLab EE versions 19.0.5, 19.1.3, and 19.2.1 and later.
Potential Impact
The vulnerability allows an authenticated user to bypass branch protection mechanisms by merging code into protected branches without the required approvals. This can lead to unauthorized code changes being introduced, impacting the integrity of the codebase. There is no impact on confidentiality or availability reported. No known exploits in the wild have been identified.
Mitigation Recommendations
A fix is available. Users should upgrade to GitLab EE versions 19.0.5, 19.1.3, or 19.2.1 or later to remediate this vulnerability. Applying these official fixes will prevent exploitation of the race condition in approval rule processing.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-629v-rwjx-m485
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-13113"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6ae5339c2644c7f89866d0
Added to database: 07/30/2026, 05:46:27 UTC
Last enriched: 07/30/2026, 07:04:06 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 9
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.