Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-26412

Removed group members were able to use the To-Do functionality to retrieve updated information on confidential epics starting in GitLab EE…

Low3.1EPSS 1.0%
Published
Updated
Reserved
Assigned by
GitLab

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.

Timeline

  1. ID reserved

    By GitLab

  2. · 2 months later

    Published

  3. · 4 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-26412, by who scored it
Scored byCVSSScoreVector
GitLabCNA (assigner)3.1Low3.1CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
NVDNVD · Modified3.1Medium4.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
1.0% · top 37% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.1.

Weakness

  • Information exposure in GitLab EE

Affected products

  • GitLab · GitLab EE

    • affected >=13.2, <13.4.7
    • affected >=13.5, <13.5.5
    • affected >=13.6, <13.6.2

References (2)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-26412 badge
[![CVE-2020-26412](https://trackcve.app/badge/CVE-2020-26412.svg)](https://trackcve.app/cve/CVE-2020-26412)

Record last updated .