CVE-2021-21411: OAuth2-Proxy's `--gitlab-group` GitLab Group Authorization config flag stopped working in v7.0.0
The --gitlab-group flag for group-based authorization in the GitLab provider stopped working in the v7.0.0 release. Regardless of the flag settings, authorization wasn't restricted. Additionally, any authenticated users had whichever groups were set in --gitlab-group added to the new X-Forwarded-Groups header to the upstream application.
Published Jul 30, 2025
Affected packages
github.com/oauth2-proxy/oauth2-proxy/v7
- Ecosystem
- Go
- Affected
- < 7.1.0
- Fixed in
- 7.1.0
- Check
go list -m github.com/oauth2-proxy/oauth2-proxy/v7
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
The --gitlab-group flag for group-based authorization in the GitLab provider stopped working in the v7.0.0 release.
Regardless of the flag settings, authorization wasn't restricted. Additionally, any authenticated users had whichever groups were set in --gitlab-group added to the new X-Forwarded-Groups header to the upstream application.
While adding GitLab project based authorization support in #630, a bug was introduced where the user session's groups field was populated with the --gitlab-group config entries instead of pulling the individual user's group membership from the GitLab Userinfo endpoint. When the session groups where compared against the allowed groups for authorization, they matched improperly (since both lists were populated with the same data) so authorization was allowed.
Impact
This impacts GitLab Provider users who relies on group membership for authorization restrictions. Any authenticated users in your GitLab environment can access your applications regardless of --gitlab-group membership restrictions.
Patches
This is patched in v7.1.0
Workarounds
There is no workaround for the Group membership bug. But --gitlab-project can be set to use Project membership as the authorization checks instead of groups; it is not broken.
Credited to bohrasd.
References
- https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-652x-m2gr-hppm
- https://nvd.nist.gov/vuln/detail/CVE-2021-21411
- https://github.com/oauth2-proxy/oauth2-proxy/commit/0279fa7dff1752f1710707dbd1ffac839de8bbfc
- https://docs.gitlab.com/ee/user/group
- https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.1.0
- https://pkg.go.dev/github.com/oauth2-proxy/oauth2-proxy/v7
- https://github.com/advisories/GHSA-652x-m2gr-hppm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-40574
OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims
medium6.8Apr 15, 2026CVE-2026-40575
OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
critical9.1Apr 15, 2026CVE-2026-41059
OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
high8.2Apr 15, 2026CVE-2026-34454
OAuth2 Proxy's session cookies are not cleared when rendering sign-in page
low3.5Apr 14, 2026CVE-2026-34457
OAuth2 Proxy's Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
critical9.1No fixApr 14, 2026CVE-2025-64484
OAuth2-Proxy is vulnerable to header smuggling via underscore leading to potential privilege escalation
high8.5Nov 12, 2025
