CVE-2024-6678

Public Exploit
Authentication Bypass by Spoofing in GitLab

Description

An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.

Remediation

Solution:

  • Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above.

Category

9.9
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 0.06%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/471923 broken link issue tracking permissions required
https://hackerone.com/reports/2595495 exploit permissions required technical description
https://about.gitlab.com/releases/2024/09/11/patch-release-gitlab-17-3-2-released/

Frequently Asked Questions

What is the severity of CVE-2024-6678?
CVE-2024-6678 has been scored as a critical severity vulnerability.
How to fix CVE-2024-6678?
To fix CVE-2024-6678: Upgrade to versions 17.1.7, 17.2.5, 17.3.2 or above.
Is CVE-2024-6678 being actively exploited in the wild?
It is possible that CVE-2024-6678 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-6678?
CVE-2024-6678 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.