Medium [CVE-2026-4398] Authorization Bypass Through User-Controlled Key in GitLab
This medium-severity GitLab advisory covers CVE-2026-4398 affecting GitLab.
Android app · Google Play
Monitor future GitLab CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.
- GitLab 18.3 before 19.1.7
- GitLab 19.2 before 19.2.5
- GitLab 19.3 before 19.3.1
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
- 19.1.7
- 19.2.5
- 19.3.1
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation
Upgrade to a fixed release: 19.1.7, 19.2.5, 19.3.1. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.