CVE-2020-26416 json
Information disclosure in Advanced Search component of GitLab EE starting from 8.4 results in exposure of search terms via Rails logs.
published 5y ago modified last mo. also BIT-gitlab-2020-26416 , EUVD-2020-18963
- cvss
- 4.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
Information disclosure in Advanced Search component of GitLab EE starting from 8.4 results in exposure of search terms via Rails logs. This affects versions >=8.4 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <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-26416 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 FencerExploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.0 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 4.0 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=8.4.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
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
- Technology feeds
References
-
gitlab.com
/gitlab-org/gitlab/-/issues/244495
broken-link, web
-
gitlab.com
/gitlab-org/cves/-/blob/master/2020/CVE-2020-26416.json
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-26416
web
Sources
- CVE List CVE-2020-26416
- NVD CVE-2020-26416
- OSV BIT-gitlab-2020-26416
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.