CVE-2023-0756Network attack vector

Client code execution via crafted repository name

Published May 3, 2023 · Updated Feb 12, 2025

Code injection in GitLab before 15.9.6, 15.10 through 15.10.4, and 15.11.0 allows remote authenticated users to execute code on victims' systems. The public record identifies the main branch and an attacker-controlled repository name as the trigger, but does not disclose the server-side function or transformation that turns the name into executable repository content. A low-privileged account must create the repository and a victim must clone or download it; execution occurs on that victim's system, not on the GitLab server.

CVSS severity4.8
Medium
EPSS probability1.01%
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

Code injection in GitLab before 15.9.6, 15.10 through 15.10.4, and 15.11.0 allows remote authenticated users to execute code on victims' systems. The public record identifies the main branch and an attacker-controlled repository name as the trigger, but does not disclose the server-side function or transformation that turns the name into executable repository content. A low-privileged account must create the repository and a victim must clone or download it; execution occurs on that victim's system, not on the GitLab server.

The record

CVE
CVE-2023-0756
Published
May 3, 2023
Updated
Feb 12, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-94, T1204
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 3, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 12, 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=>=15.10, <15.10.5
  2. Affected versionversion=>=15.11, <15.11.1
  3. Affected versionversion=<15.9.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=15.10, <15.10.5; version=>=15.11, <15.11.1; version=<15.9.6

Published CVSS scores

4.8GitLabCVSS:3.1/AV:N/AC:H/PR:L/UI:R/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-94Improper Control of Generation of Code ('Code Injection')
T1204User Execution

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