CVE-2020-26412

Description

Removed group members were able to use the To-Do functionality to retrieve updated information on confidential epics starting in GitLab EE 13.2 before 13.6.2.

3.1

CVSS

Severity: Low

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.13%

Vendor Advisory gitlab.com

Affected: GitLab GitLab EE

References

Link	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/228670	broken link
https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-26412.json	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-26412?: CVE-2020-26412 has been scored as a low severity vulnerability.
How to fix CVE-2020-26412?: To fix CVE-2020-26412, 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-2020-26412 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-26412 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-2020-26412?: CVE-2020-26412 affects GitLab GitLab EE.

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.