CVE-2024-6502Public exploitNetwork attack vector

Release archive substitution via stale deleted-tag association

Published Aug 22, 2024 · Updated Aug 29, 2024

Improper release-reference handling in GitLab CE/EE allows remote authenticated users to substitute source archives after a tag is deleted. Git::TagPushService does not invoke Releases::DestroyService for a tag deleted by Git push, leaving the release bound to a ref name that a new branch can reuse. Developer access and a victim who downloads the displayed release archive are required; the archive can contain content different from the commit shown in the web interface.

CVSS severity5.7
Medium
EPSS probability0.37%
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 release-reference handling in GitLab CE/EE allows remote authenticated users to substitute source archives after a tag is deleted. Git::TagPushService does not invoke Releases::DestroyService for a tag deleted by Git push, leaving the release bound to a ref name that a new branch can reuse. Developer access and a victim who downloads the displayed release archive are required; the archive can contain content different from the commit shown in the web interface.

The record

CVE
CVE-2024-6502
Published
Aug 22, 2024
Updated
Aug 29, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-684, T1195.002, T1204.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 22, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 29, 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=17.2 <17.2.4
  2. Affected versionversion=17.3 <17.3.1
  3. Affected versionversion=8.2 <17.1.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=17.2 <17.2.4; version=17.3 <17.3.1; version=8.2 <17.1.6

Published CVSS scores

6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
5.7GitLab Inc.CVSS:3.1/AV:N/AC:L/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 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

CWE-684Incorrect Provision of Specified Functionality
T1195.002Compromise Software Supply Chain
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