Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-9596

Inclusion of Sensitive Information in Source Code in GitLab

Low3.7EPSS 0.32%
Published
Updated
Reserved
Assigned by
GitLab

Description

An issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. It was possible for an unauthenticated attacker to determine the GitLab version number for a GitLab instance.

Scores

CVSS scores of CVE-2024-9596, by who scored it
Scored byCVSSScoreVector
GitLabCNA (assigner)3.1Low3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVDNVD · Analyzed3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (4 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.7.

Weakness

Affected products

  • GitLab · GitLab

    • affected 16.6 – < 17.2.9
    • affected 17.3 – < 17.3.5
    • affected 17.4 – < 17.4.2

What to do

Solution: Upgrade to version 17.2.9, 17.3.5 or 17.4.2

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-9596 badge
[![CVE-2024-9596](https://trackcve.app/badge/CVE-2024-9596.svg)](https://trackcve.app/cve/CVE-2024-9596)

Record last updated .