What is the severity of CVE-2020-26415?

CVE-2020-26415 is considered a medium severity vulnerability affecting specific versions of GitLab.

How do I fix CVE-2020-26415?

To fix CVE-2020-26415, upgrade GitLab to a version equal to or greater than 13.4.7, 13.5.5, or 13.6.2.

What type of data is exposed in CVE-2020-26415?

CVE-2020-26415 exposes information about starred projects for private user profiles via the GraphQL API.

Which versions of GitLab are affected by CVE-2020-26415?

CVE-2020-26415 affects GitLab versions greater than or equal to 12.2 and less than 13.4.7, along with specific ranges for 13.5 and 13.6.

Is CVE-2020-26415 specific to a certain GitLab edition?

CVE-2020-26415 affects both the community and enterprise editions of GitLab.

Vulnerability/
CVE-2020-26415

medium

4.3

CWE

200 862

11/12/2020

4/8/2024

CVE-2020-26415: Infoleak

First published: Fri Dec 11 2020(Updated: )

Information about the starred projects for private user profiles was exposed via the GraphQL API starting from 12.2 via the REST API. This affects GitLab >=12.2 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <13.6.2.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.2.0<13.4.7
GitLab	>=12.2.0<13.4.7
GitLab	>=13.5.0<13.5.5
GitLab	>=13.5.0<13.5.5
GitLab	>=13.6.0<13.6.2
GitLab	>=13.6.0<13.6.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-26415?
CVE-2020-26415 is considered a medium severity vulnerability affecting specific versions of GitLab.
How do I fix CVE-2020-26415?
To fix CVE-2020-26415, upgrade GitLab to a version equal to or greater than 13.4.7, 13.5.5, or 13.6.2.
What type of data is exposed in CVE-2020-26415?
CVE-2020-26415 exposes information about starred projects for private user profiles via the GraphQL API.
Which versions of GitLab are affected by CVE-2020-26415?
CVE-2020-26415 affects GitLab versions greater than or equal to 12.2 and less than 13.4.7, along with specific ranges for 13.5 and 13.6.
Is CVE-2020-26415 specific to a certain GitLab edition?
CVE-2020-26415 affects both the community and enterprise editions of GitLab.

agent/references
agent/type
agent/author
agent/weakness
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/12.2.0
version/gitlab/13.5.0
version/gitlab/13.6.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-26415?
CVE-2020-26415 is considered a medium severity vulnerability affecting specific versions of GitLab.
How do I fix CVE-2020-26415?
To fix CVE-2020-26415, upgrade GitLab to a version equal to or greater than 13.4.7, 13.5.5, or 13.6.2.
What type of data is exposed in CVE-2020-26415?
CVE-2020-26415 exposes information about starred projects for private user profiles via the GraphQL API.
Which versions of GitLab are affected by CVE-2020-26415?
CVE-2020-26415 affects GitLab versions greater than or equal to 12.2 and less than 13.4.7, along with specific ranges for 13.5 and 13.6.
Is CVE-2020-26415 specific to a certain GitLab edition?
CVE-2020-26415 affects both the community and enterprise editions of GitLab.