CVE-2022-3639

Description

A potential DOS vulnerability was discovered in GitLab CE/EE affecting all versions from 10.8 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2. Improper data handling on branch creation could have been used to trigger high CPU usage.

Category

4.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.02%
Third-Party Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/366876 broken link
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3639.json vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-3639?
CVE-2022-3639 has been scored as a medium severity vulnerability.
How to fix CVE-2022-3639?
To fix CVE-2022-3639, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-3639 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-3639 is being actively exploited. 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-2022-3639?
CVE-2022-3639 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.