CVE-2023-2013Public exploitNetwork attack vector

Victim code execution via ambiguous branch names

Published Jun 7, 2023 · Updated Jan 7, 2025

Improper branch-name handling in affected GitLab releases allows remote authenticated users to trick victims into cloning untrusted code. GitLab renders refs/heads/main when heads/main is the default branch, while Git clone resolves that short name to refs/heads/heads/main. A user with project write access must create both branches and persuade a victim to clone the repository and execute its contents, enabling attacker-controlled code execution on the victim's system.

CVSS severity2.6
Low
EPSS probability0.69%
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

Improper branch-name handling in affected GitLab releases allows remote authenticated users to trick victims into cloning untrusted code. GitLab renders refs/heads/main when heads/main is the default branch, while Git clone resolves that short name to refs/heads/heads/main. A user with project write access must create both branches and persuade a victim to clone the repository and execute its contents, enabling attacker-controlled code execution on the victim's system.

The record

CVE
CVE-2023-2013
Published
Jun 7, 2023
Updated
Jan 7, 2025
Vendor
GitLab
Product
GitLab
Classifications
T1204.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 7, 2023CVE publishedPublication date reported by the CVE source.
  2. Jan 7, 2025Record 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=>=1.2, <15.10.8
  2. Affected versionversion=>=15.11, <15.11.7
  3. Affected versionversion=>=16.0, <16.0.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=1.2, <15.10.8; version=>=15.11, <15.11.7; version=>=16.0, <16.0.2

Published CVSS scores

2.6GitLabCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1204.002Malicious File

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