CVE-2024-4024Network attack vector

Account takeover via mutable Bitbucket usernames

Published Apr 25, 2024 · Updated Jun 2, 2026

Authentication bypass in affected GitLab CE/EE releases allows remote authenticated users to take over accounts linked to Bitbucket. GitLab linked Bitbucket identities using the account's mutable username instead of its immutable UUID, allowing a username reassignment to resolve to another user's linkage. Exploitation requires valid Bitbucket credentials, user interaction, and a GitLab instance configured to use Bitbucket as an OAuth 2.0 provider; successful exploitation permits access to and modification of the victim's GitLab data.

CVSS severity7.3
High
EPSS probability14.90%
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

Authentication bypass in affected GitLab CE/EE releases allows remote authenticated users to take over accounts linked to Bitbucket. GitLab linked Bitbucket identities using the account's mutable username instead of its immutable UUID, allowing a username reassignment to resolve to another user's linkage. Exploitation requires valid Bitbucket credentials, user interaction, and a GitLab instance configured to use Bitbucket as an OAuth 2.0 provider; successful exploitation permits access to and modification of the victim's GitLab data.

The record

CVE
CVE-2024-4024
Published
Apr 25, 2024
Updated
Jun 2, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-302, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 25, 2024CVE publishedPublication date reported by the CVE source.
  2. Jun 2, 2026Record 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=16.10 <16.10.4
  2. Affected versionversion=16.11 <16.11.1
  3. Affected versionversion=7.8 <16.9.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=16.10 <16.10.4; version=16.11 <16.11.1; version=7.8 <16.9.6

Published CVSS scores

7.3GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
8.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 exploitUnconfirmed

Weakness, pattern, technique

CWE-302Authentication Bypass by Assumed-Immutable Data
T1078Valid Accounts

Public exploit references

No public exploit references are available in this record.

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