CVE-2023-4379Public exploitNetwork attack vector

Protected-branch changes via retained Code Owner approvals

Published Nov 9, 2023 · Updated Jun 2, 2026

Incorrect authorization in affected GitLab EE releases allows remote authenticated users to bypass Code Owner approval on merge requests. The target-branch update path leaves existing approvals intact when the project is configured to remove Code Owner approvals after relevant files change. Exploitation requires a Developer who can retarget a previously approved merge request, allowing changes to enter a protected branch without renewed Code Owner review.

CVSS severity8.1
High
EPSS probability0.50%
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

Incorrect authorization in affected GitLab EE releases allows remote authenticated users to bypass Code Owner approval on merge requests. The target-branch update path leaves existing approvals intact when the project is configured to remove Code Owner approvals after relevant files change. Exploitation requires a Developer who can retarget a previously approved merge request, allowing changes to enter a protected branch without renewed Code Owner review.

The record

CVE
CVE-2023-4379
Published
Nov 9, 2023
Updated
Jun 2, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-863, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 9, 2023CVE publishedPublication date reported by the CVE source.
  2. Jun 2, 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=15.3 <16.2.8
  2. Affected versionversion=16.3 <16.3.5
  3. Affected versionversion=16.4 <16.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=15.3 <16.2.8; version=16.3 <16.3.5; version=16.4 <16.4.1

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
8.1GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/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-863Incorrect Authorization
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