CVE-2023-6051Public exploitNetwork attack vector

Code injection via commit-like tag name

Published Dec 15, 2023 · Updated Nov 20, 2025

Code injection in GitLab CE/EE before 16.4.4, 16.5 before 16.5.4, and 16.6 before 16.6.2 allows remote authenticated users to alter tag archives. The web interface treats a tag name resembling a long commit hash as the displayed commit while archive generation resolves the same name as a tag pointing to different content. Developer access to create the crafted tag is sufficient, and code execution occurs only if another user trusts, downloads, and runs the substituted content.

CVSS severity5.7
Medium
EPSS probability0.63%
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 CE/EE before 16.4.4, 16.5 before 16.5.4, and 16.6 before 16.6.2 allows remote authenticated users to alter tag archives. The web interface treats a tag name resembling a long commit hash as the displayed commit while archive generation resolves the same name as a tag pointing to different content. Developer access to create the crafted tag is sufficient, and code execution occurs only if another user trusts, downloads, and runs the substituted content.

The record

CVE
CVE-2023-6051
Published
Dec 15, 2023
Updated
Nov 20, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-94, T1195.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 15, 2023CVE publishedPublication date reported by the CVE source.
  2. Nov 20, 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=0 <16.4.4
  2. Affected versionversion=16.5 <16.5.4
  3. Affected versionversion=16.6 <16.6.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=0 <16.4.4; version=16.5 <16.5.4; version=16.6 <16.6.2

Published CVSS scores

5.7GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
6.5NIST NVDCVSS:3.1/AV:N/AC:L/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-94Improper Control of Generation of Code ('Code Injection')
T1195.002Compromise Software Supply Chain

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