Skip to content
Emerging threatsMedium

CVE-2020-10977Gitlab Path Traversal

GitLab EE/CE 8.5 to 12.9 is vulnerable to a an path traversal when moving an issue between projects.

Published Apr 8, 2020 · Updated Sep 8, 2026 · Also known as BIT-gitlab-2020-10977, UBUNTU-CVE-2020-10977

Key Facts

Routine patching
  • CVE-2020-10977 is a medium-severity vulnerability (CVSS 5.5 v3.1) affecting Gitlab.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 43% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Gitlab 12.9.1, Gitlab 13.2.3-2, Gitlab <=12.9.
  • Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Scores

CVSS v3.1

5.5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS (30-day exploit likelihood)

43%

Higher than 98.7% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

55/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Weaponized

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

GitLab EE/CE 8.5 to 12.9 is vulnerable to a an path traversal when moving an issue between projects.

Affected Products

5 affected entries in total
ProductAffected versionsFixed in
GitlabGitlab>= 8.5.012.9

Patched Releases

Gitlab

12.9.1, 13.2.3-2, <=12.9

Timeline

  1. Publicly disclosed

    Apr 8, 2020

  2. Last updated

    Sep 8, 2026

Weakness Type

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

FAQ

Common Questions.

Is CVE-2020-10977 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.