Quick answers
- Is CVE-2026-105458 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105458 being exploited in the wild.
- How severe is CVE-2026-105458?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- GitLab EE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.
- Is there a fix for CVE-2026-105458?
- Yes: fixed in GitLab EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105458 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105458?
- Check whether you run GitLab or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: GitLab EE 19.2.8, 19.3.5, 19.4.2
Technical details
An authenticated user holding a specific granular permission can obtain a GitLab Duo Agent Platform token that bypasses governance controls due to reliance on untrusted input in a security decision. This is an incorrect authorization issue affecting GitLab EE versions 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. A network attack vector with authentication required; exploitation results in governance control bypass.
Affected products
- GitLab GitLab EE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2
Timeline
- 2026-10-13: disclosed
- 2026-10-12: patched