CVE-2024-6595Public exploitNetwork attack vector

Package integrity bypass via conflicting NPM metadata

Published Jul 17, 2024 · Updated Sep 17, 2024

Package confusion in GitLab 11.8 through 16.11.5, 17.0 through 17.0.3, and 17.1 through 17.1.1 allows remote authenticated users to mislabel packages. The NPM registry upload API accepts manifest metadata separately from the tarball's package.json and fails to verify matching names, versions, dependencies, or scripts. A user able to publish a package can hide install scripts or dependencies from registry views, and a consumer must install the package for code or altered dependency data to take effect.

CVSS severity3.0
Low
EPSS probability0.46%
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

Package confusion in GitLab 11.8 through 16.11.5, 17.0 through 17.0.3, and 17.1 through 17.1.1 allows remote authenticated users to mislabel packages. The NPM registry upload API accepts manifest metadata separately from the tarball's package.json and fails to verify matching names, versions, dependencies, or scripts. A user able to publish a package can hide install scripts or dependencies from registry views, and a consumer must install the package for code or altered dependency data to take effect.

The record

CVE
CVE-2024-6595
Published
Jul 17, 2024
Updated
Sep 17, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-434, CWE-451, T1195.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 17, 2024CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 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=11.8 <16.11.6
  2. Affected versionversion=17.0 <17.0.4
  3. Affected versionversion=17.1 <17.1.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=11.8 <16.11.6; version=17.0 <17.0.4; version=17.1 <17.1.2

Published CVSS scores

3.0GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N
5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 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-434Unrestricted Upload of File with Dangerous Type
CWE-451User Interface (UI) Misrepresentation of Critical Information
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