Oauth2 Proxy Project Oauth2 Proxy vulnerabilities
8 known vulnerabilities affecting oauth2_proxy_project/oauth2_proxy.
Total CVEs
8
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL1HIGH1MEDIUM6
Vulnerabilities
Page 1 of 1
CVE-2025-54576CRITICALCVSS 9.1fixed in 7.11.02025-07-30
CVE-2025-54576 [CRITICAL] CWE-290 CVE-2025-54576: OAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middlewar
OAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. In versions 7.10.0 and below, oauth2-proxy deployments are vulnerable when using the skip_auth_routes configuration option with regex patterns. Attackers can bypass authenti
nvd
CVE-2021-21411MEDIUMCVSS 5.5≥ 7.0.0, < 7.1.02021-03-26
CVE-2021-21411 [MEDIUM] CWE-863 CVE-2021-21411: OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or oth
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 g
nvd
CVE-2021-21291MEDIUMCVSS 6.1fixed in 7.0.02021-02-02
CVE-2021-21291 [MEDIUM] CWE-601 CVE-2021-21291: OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication usi
OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. In OAuth2 Proxy before version 7.0.0, for users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have bee
nvd
CVE-2020-4037MEDIUMCVSS 5.4≥ 5.1.1, < 6.0.02020-06-29
CVE-2020-4037 [MEDIUM] CWE-601 CVE-2020-4037: In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address
In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access. This redirect URL is checked within the proxy and validated before redirecting the user t
nvd
CVE-2020-11053MEDIUMCVSS 6.1fixed in 5.1.12020-05-07
CVE-2020-11053 [MEDIUM] CWE-601 CVE-2020-11053: In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. Users can provide a redirect
In 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 user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access. This redirect URL is checked within the proxy and validated before redirecting th
nvd
CVE-2020-5233MEDIUMCVSS 6.1fixed in 5.0.02020-01-30
CVE-2020-5233 [MEDIUM] CWE-601 CVE-2020-5233: OAuth2 Proxy before 5.0 has an open redirect vulnerability. Authentication tokens could be silently
OAuth2 Proxy before 5.0 has an open redirect vulnerability. Authentication tokens could be silently harvested by an attacker. This has been patched in version 5.0.
nvd
CVE-2017-1000069HIGHCVSS 8.8v2.12017-07-17
CVE-2017-1000069 [HIGH] CWE-352 CVE-2017-1000069: CSRF in Bitly oauth2_proxy 2.1 during authentication flow
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
nvd
CVE-2017-1000070MEDIUMCVSS 6.1≤ 2.12017-07-17
CVE-2017-1000070 [MEDIUM] CWE-601 CVE-2017-1000070: The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability dur
The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819
nvd