Quick answers
- Is CVE-2026-104661 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104661 being exploited in the wild.
- How severe is CVE-2026-104661?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- GitLab EE 17.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1.
- Is there a fix for CVE-2026-104661?
- Yes: fixed in GitLab EE 19.4.2, 19.3.5, 19.2.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104661 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104661?
- 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.4.2, 19.3.5, 19.2.8
Technical details
An authenticated user with a custom role holding compliance framework administration permissions could exploit improper privilege assignment to configure and execute a specially crafted compliance pipeline across group projects. The vulnerability stems from inadequate authorization checks that fail to properly enforce permission boundaries for custom role privileges. A fix is available in versions 19.4.2, 19.3.5, and 19.2.8.
Affected products
- GitLab GitLab EE 17.0 to 19.2.7, 19.3.0 to 19.3.4, 19.4.0 to 19.4.1
Timeline
- 2026-10-13: disclosed
- 2026-10-12: patched