Skip to main content
VulnerabilityPublished Updated

CVE-2024-7554: Exposure of Sensitive Information to an Unauthorized Actor in GitLab

Affects gitlabSource GCVE Database

0

Not known to be exploited · fixed in 17.2.2 : update gitlab when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.2.2, 17.1.4, 17.0.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade gitlab to 17.2.2, 17.1.4 or 17.0.6.

Affected software

ProductAffectedFixed in
Bitnamigitlabpkg:bitnami/gitlabOther threatsAffected
  • >=13.9.0 <17.0.6
  • >=17.1.0 <17.1.4
  • >=17.2.0 <17.2.2
Fixed in
  • 17.0.6
  • 17.1.4
  • 17.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading GitLab to version 17.0.6, 17.1.4, or 17.2.2 or later. These versions contain the fix that prevents access tokens from being logged improperly. No additional mitigation is required if the system is updated.

Description

A vulnerability in GitLab CE/EE allows exposure of access tokens to unauthorized actors due to logging under certain API request conditions. This affects multiple version ranges prior to specific patched releases. The issue has been addressed in GitLab versions 17.0.6, 17.1.4, and 17.2.2.

References

Community reviews

Loading reviews…