CVE-2024-5258

CVE-2024-5258 is a medium-severity vulnerability in Gitlab with a CVSS 3.x base score of 4.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-863.

Key facts

Description

An authorization vulnerability exists within GitLab from versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1 where an authenticated attacker could utilize a crafted naming convention to bypass pipeline authorization logic.

Frequently asked questions

What is CVE-2024-5258?
An authorization vulnerability exists within GitLab from versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1 where an authenticated attacker could utilize a crafted naming convention to bypass pipeline authorization logic.
How severe is CVE-2024-5258?
CVE-2024-5258 has a CVSS 3.x base score of 4.4, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2024-5258 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-5258?
CVE-2024-5258 primarily affects Gitlab. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-5258?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-5258 have an EU (EUVD) identifier?
Yes. CVE-2024-5258 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-46496.
When was CVE-2024-5258 published?
CVE-2024-5258 was published on 2024-05-23 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-863 (Incorrect Authorization) vulnerabilities

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →