CVE-2026-110990 json
Insertion of Sensitive Information into Log File in GitLab
published 2d ago modified yesterday also EUVD-2026-126855
- cvss
- 2.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1.7 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed sensitive credential values submitted in GraphQL requests to be written to logs in plaintext due to incomplete filtering of sensitive data.
Patch / fix
- GitLab GitLab 19.3.9, 19.4.8, 19.5.6
Is CVE-2026-110990 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- hackerone.com https://hackerone.com/reports/4044243 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.3 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
- Technology feeds
References
-
hackerone.com
/reports/4044243
technical-description, exploit, permissions-required
- gitlab.com /gitlab-org/gitlab/-/work_items/633981
- docs.gitlab.com /releases/patches/patch-release-gitlab-19-5-6-released/
Sources
- CVE List CVE-2026-110990
- NVD CVE-2026-110990
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.