CVE-2026-13113Network attack vectorHinoki check available

Protected-branch merge bypass via approval-processing race

Published Jul 29, 2026 · Updated Jul 29, 2026

Race condition in GitLab EE 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows remote authenticated users to bypass approvals. GitLab identifies approval rule processing as the affected locus but has not disclosed the exact racing operations or configuration preconditions. An authenticated account and the undisclosed conditions are required; exploitation writes unapproved code to a protected branch, affecting repository integrity.

CVSS severity6.5
Medium
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in GitLab EE 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows remote authenticated users to bypass approvals. GitLab identifies approval rule processing as the affected locus but has not disclosed the exact racing operations or configuration preconditions. An authenticated account and the undisclosed conditions are required; exploitation writes unapproved code to a protected branch, affecting repository integrity.

The record

CVE
CVE-2026-13113
Published
Jul 29, 2026
Updated
Jul 29, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-367, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 29, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=17.0 <19.0.5
  2. Affected versionversion=19.1 <19.1.3
  3. Affected versionversion=19.2 <19.2.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=17.0 <19.0.5; version=19.1 <19.1.3; version=19.2 <19.2.1

Published CVSS scores

6.5GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
5.3NIST NVDCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1565.001Stored Data Manipulation

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