← Vulnerability feed

Vulnerability record · CVE-2021-21411 · published 26 March 2021

CVE-2021-21411: Oauth2 proxy project oauth2 proxy incorrect authorization vulnerability

OOauth2 Proxy Project · Oauth2 Proxy

OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. 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. 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. This is patched in v7.1.0. 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.

5.5 CVSS 3.1 Medium EPSS 1.1% · top 36.5% CWE-863 · Incorrect authorization
5.5CVSS 3.1 base score, v2 5.5
1.1%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
10References
17 Jun 2026Last modified by NVD

Description

OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. 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. 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. This is patched in v7.1.0. 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.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2021-21411 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

9.1CVE-2026-40575Oauth2 proxy project oauth2 proxy authentication bypass by spoofing vulnerabilityOAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 may trust a client-supplied `X-For…EPSS 0.73%9.1CVE-2026-34457Oauth2 proxy project oauth2 proxy authentication bypass by spoofing vulnerabilityOAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions prior to 7.15.2 contain a configuration-dependent authe…EPSS 0.66%9.1CVE-2025-54576Oauth2 proxy project oauth2 proxy authentication bypass by spoofing vulnerabilityOAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse prox…EPSS 1.2%8.8CVE-2017-1000069Oauth2 proxy project oauth2 proxy cross-site request forgery vulnerabilityCSRF in Bitly oauth2_proxy 2.1 during authentication flowEPSS 0.74%8.2CVE-2026-41059Oauth2 proxy project oauth2 proxy authentication bypass via alternate path vulnerabilityOAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 have a configuration-dependent aut…EPSS 0.43%6.8CVE-2026-40574Oauth2 proxy project oauth2 proxy incorrect authorization vulnerabilityOAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Prior to 7.15.2, an authorization bypass exists in OAuth2 Proxy …EPSS 0.34%6.1CVE-2021-21291Oauth2 proxy project oauth2 proxy open redirect vulnerabilityOAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to vali…EPSS 1.6%6.1CVE-2020-11053Oauth2 proxy project oauth2 proxy open redirect vulnerabilityIn OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. Users can provide a redirect address for the proxy to send the authenticated u…EPSS 0.79%

Source: NIST National Vulnerability Database (record CVE-2021-21411), CISA KEV, FIRST EPSS (scores of 2026-09-29). This page is refreshed as NVD updates the record.