Quick answers
- Is CVE-2026-14210 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14210 being exploited in the wild.
- How severe is CVE-2026-14210?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- GitLab CE 18.11 to before 19.2.8, 19.3 to before 19.3.5, 19.4 to before 19.4.2; GitLab EE 18.11 to before 19.2.8, 19.3 to before 19.3.5, 19.4 to before 19.4.2.
- Is there a fix for CVE-2026-14210?
- Yes: fixed in GitLab CE 19.2.8, 19.3.5, 19.4.2; 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-14210 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-14210?
- Check whether you run GitLab, GitLab CE 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 CE 19.2.8, 19.3.5, 19.4.2; GitLab EE 19.2.8, 19.3.5, 19.4.2
Technical details
An authenticated attacker with a project-scoped fine-grained Personal Access Token (PAT) can exploit incorrect authorization logic in label ownership scope validation to delete or modify group-level labels they should not have access to. This is a privilege escalation via scope bypass requiring an authenticated attacker and a specially crafted PAT. A fix is available in GitLab 19.2.8, 19.3.5, and 19.4.2.
Affected products
- GitLab GitLab CE 18.11 to before 19.2.8, 19.3 to before 19.3.5, 19.4 to before 19.4.2
- GitLab GitLab EE 18.11 to before 19.2.8, 19.3 to before 19.3.5, 19.4 to before 19.4.2
Timeline
- 2026-10-13: disclosed
- 2026-10-12: patched