CVE-2026-34457
Description
OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions prior to 7.15.2 contain a configuration-dependent authentication bypass in deployments where OAuth2 Proxy is used with an auth_request-style integration (such as nginx auth_request) and either --ping-user-agent is set or --gcp-healthchecks is enabled. In affected configurations, OAuth2 Proxy treats any request with the configured health check User-Agent value as a successful health check regardless of the requested path, allowing an unauthenticated remote attacker to bypass authentication and access protected upstream resources. Deployments that do not use auth_request-style subrequests or that do not enable --ping-user-agent/--gcp-healthchecks are not affected. This issue is fixed in 7.15.2.
How to fix
- oauth2_proxy_project oauth2_proxy7.15.2 or later
- github.com/oauth2-proxy/oauth2-proxy/v77.15.2 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| oauth2_proxy_project oauth2_proxy | v < 7.15.2 | 7.15.2 |
| github.com/oauth2-proxy/oauth2-proxy/v7Go | v < 7.15.2 | 7.15.2 |
| github.com/oauth2-proxy/oauth2-proxyGo | v ≤ 3.2.0, No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.