Skip to content
Fencer Intel
low 3.1

CVE-2020-26412 json

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

published 5y ago modified 2mo ago also BIT-gitlab-2020-26412 , EUVD-2020-18959

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami gitlab 13.4.7, 13.5.5, 13.6.2
  • gitlab gitlab 13.4.7, 13.5.5, 13.6.2
  • gitlab gitlab_enterprise 13.4.7, 13.5.5, 13.6.2

Is CVE-2020-26412 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=13.2.0, <13.4.7
>=13.5.0, <13.5.5
>=13.6.0, <13.6.2
13.4.7
13.5.5
13.6.2

Affected products

  • GitLab GitLab EE

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: add affected deb and rpm records.