CVE-2022-4143Public exploitNetwork attack vector

Protected-branch modification via stale merge approval

Published Jun 28, 2023 · Updated Dec 3, 2024

Authorization bypass in GitLab 15.7 through 15.8.4, 15.9 through 15.9.3, and 15.10.0 allows remote authenticated users to merge unapproved changes. After a new commit reaches an approved merge request, asynchronous approval removal leaves the stale approval valid for 5–10 seconds and still permits merging. Exploitation requires Premium or Ultimate, the remove-approvals-on-commit setting, source-branch write access, merge permission, and successful timing of the race; arbitrary changes can enter a protected branch without renewed review.

CVSS severity6.4
Medium
EPSS probability0.76%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in GitLab 15.7 through 15.8.4, 15.9 through 15.9.3, and 15.10.0 allows remote authenticated users to merge unapproved changes. After a new commit reaches an approved merge request, asynchronous approval removal leaves the stale approval valid for 5–10 seconds and still permits merging. Exploitation requires Premium or Ultimate, the remove-approvals-on-commit setting, source-branch write access, merge permission, and successful timing of the race; arbitrary changes can enter a protected branch without renewed review.

The record

CVE
CVE-2022-4143
Published
Jun 28, 2023
Updated
Dec 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-367, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 28, 2023CVE publishedPublication date reported by the CVE source.
  2. Dec 3, 2024Record 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=>=15.10, <15.10.1
  2. Affected versionversion=>=15.7, <15.8.5
  3. Affected versionversion=>=15.9, <15.9.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=15.10, <15.10.1; version=>=15.7, <15.8.5; version=>=15.9, <15.9.4

Published CVSS scores

6.4GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/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 exploitPublished

Weakness, pattern, technique

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

Public exploit references

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