CVE-2026-101358 json
Incorrect Authorization in GitLab
published 2d ago modified yesterday also EUVD-2026-126866
- cvss
- 3.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 17.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read CI/CD variable metadata from projects they did not have access to due to improper authorization in pipeline execution policies.
Patch / fix
- GitLab GitLab 19.3.9, 19.4.8, 19.5.6
Is CVE-2026-101358 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.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3872297 referenced PoC, tagged "exploit" by a source, unverified
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 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
hackerone.com
/reports/3872297
technical-description, exploit, permissions-required
- gitlab.com /gitlab-org/gitlab/-/work_items/631131
- docs.gitlab.com /releases/patches/patch-release-gitlab-19-5-6-released/
Sources
- CVE List CVE-2026-101358
- NVD CVE-2026-101358
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.