CVE-2020-26412 Information disclosure in GitLab EE
Removed group members could access confidential epic updates via the To-Do feature, exposing sensitive project information to unauthorized users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-26412?
CVE-2020-26412 is a low-severity vulnerability in Gitlab Gitlab, published on 11 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2020-26412?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.2.0 | 13.4.7, 13.5.5, 13.6.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2020-26412?
Upgrade gitlab to a fixed version for your release line: 13.4.7, 13.5.5 or 13.6.2.
Is CVE-2020-26412 being exploited?
There is no known exploitation of CVE-2020-26412 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2020-26412, GHSA-66h6-4ppg-82p8, UBUNTU-CVE-2020-26412.