Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
OAuth2-Proxy versions before 7.1.0 have a flaw in the GitLab provider where the `--gitlab-group` authorization setting stopped working in v7.0.0. Any user who authenticates through GitLab can access the protected application regardless of group membership, and the configured groups are passed to the upstream application in the X-Forwarded-Groups header. Upgrade to 7.1.0. No workaround for the group check is available, but the `--gitlab-project` setting can be used for project-based authorization instead.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.011, the 65th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-652x-m2gr-hppm
- OSV: GHSA-652x-m2gr-hppm
- github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-652x-m2gr-hppm
- nvd.nist.gov/vuln/detail/CVE-2021-21411
- github.com/oauth2-proxy/oauth2-proxy/commit/0279fa7dff1752f1710707dbd1ffac839de8bbfc
- docs.gitlab.com/ee/user/group
- github.com/oauth2-proxy/oauth2-proxy
- github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.1.0
- pkg.go.dev/github.com/oauth2-proxy/oauth2-proxy/v7