Cross-user merge commit actions via pipeline race
Published Sep 16, 2026 · Updated Sep 16, 2026
Race condition in GitLab CE/EE merge request pipeline creation allows remote authenticated users to act in another user’s commit context. GitLab has not disclosed which competing state operations become unsynchronized, beyond locating the race in pipeline creation. Successful exploitation requires Developer access, targeted user interaction, and winning a high-complexity race; it exposes or changes data reachable through the other user’s merge request commit.
Summary
What happened
Race condition in GitLab CE/EE merge request pipeline creation allows remote authenticated users to act in another user’s commit context. GitLab has not disclosed which competing state operations become unsynchronized, beyond locating the race in pipeline creation. Successful exploitation requires Developer access, targeted user interaction, and winning a high-complexity race; it exposes or changes data reachable through the other user’s merge request commit.
The record
- CVE
- CVE-2024-11222
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-362, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=13.0 <19.1.8
- Affected versionversion=19.2 <19.2.6
- Affected versionversion=19.3 <19.3.2
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