What is the severity of CVE-2020-26409?

CVE-2020-26409 is classified as a denial-of-service (DoS) vulnerability.

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

CVE-2020-26409 affects GitLab CE/EE versions from 10.3 to 13.4.7, 13.5 to 13.5.5, and 13.6 to 13.6.2.

How do I fix CVE-2020-26409?

To address CVE-2020-26409, upgrade your GitLab instance to the latest version beyond 13.4.7, 13.5.5, or 13.6.2.

What type of attack is possible due to CVE-2020-26409?

CVE-2020-26409 allows attackers to trigger uncontrolled resource consumption through input validation bypass in markdown fields.

How can I verify if I am impacted by CVE-2020-26409?

You can verify your GitLab version against the affected versions listed under CVE-2020-26409.

Vulnerability/
CVE-2020-26409

medium

6.5

CWE

20 400

11/12/2020

4/8/2024

CVE-2020-26409: Input Validation

First published: Fri Dec 11 2020(Updated: )

A DOS vulnerability exists in Gitlab CE/EE >=10.3, <13.4.7,>=13.5, <13.5.5,>=13.6, <13.6.2 that allows an attacker to trigger uncontrolled resource by bypassing input validation in markdown fields.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.3.0<13.4.7
GitLab	>=10.3.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-26409?
CVE-2020-26409 is classified as a denial-of-service (DoS) vulnerability.
Which versions of GitLab are affected by CVE-2020-26409?
CVE-2020-26409 affects GitLab CE/EE versions from 10.3 to 13.4.7, 13.5 to 13.5.5, and 13.6 to 13.6.2.
How do I fix CVE-2020-26409?
To address CVE-2020-26409, upgrade your GitLab instance to the latest version beyond 13.4.7, 13.5.5, or 13.6.2.
What type of attack is possible due to CVE-2020-26409?
CVE-2020-26409 allows attackers to trigger uncontrolled resource consumption through input validation bypass in markdown fields.
How can I verify if I am impacted by CVE-2020-26409?
You can verify your GitLab version against the affected versions listed under CVE-2020-26409.

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/10.3.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-26409?
CVE-2020-26409 is classified as a denial-of-service (DoS) vulnerability.
Which versions of GitLab are affected by CVE-2020-26409?
CVE-2020-26409 affects GitLab CE/EE versions from 10.3 to 13.4.7, 13.5 to 13.5.5, and 13.6 to 13.6.2.
How do I fix CVE-2020-26409?
To address CVE-2020-26409, upgrade your GitLab instance to the latest version beyond 13.4.7, 13.5.5, or 13.6.2.
What type of attack is possible due to CVE-2020-26409?
CVE-2020-26409 allows attackers to trigger uncontrolled resource consumption through input validation bypass in markdown fields.
How can I verify if I am impacted by CVE-2020-26409?
You can verify your GitLab version against the affected versions listed under CVE-2020-26409.