CVE-2020-26413: Infoleak
First published: Fri Dec 11 2020(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 13.6.2. Information disclosure via GraphQL results in user email being unexpectedly visible.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.4.0<13.6.2 | |
| GitLab | >=13.4.0<13.6.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-26413?
CVE-2020-26413 is classified as a medium severity vulnerability due to information disclosure risks.
How do I fix CVE-2020-26413?
To fix CVE-2020-26413, upgrade your GitLab installation to version 13.6.2 or later.
What kind of information is exposed by CVE-2020-26413?
CVE-2020-26413 may lead to unauthorized visibility of user email addresses through GraphQL queries.
Which versions of GitLab are affected by CVE-2020-26413?
CVE-2020-26413 affects all GitLab CE/EE versions from 13.4.0 up to, but not including, 13.6.2.
Is there a workaround for CVE-2020-26413 before applying the fix?
There is no official workaround for CVE-2020-26413, so upgrading is the recommended approach.
- agent/type
- agent/references
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/13.4.0