Homepage

Authentication Bypass Affecting oauth2-proxy-advanced-compat package, versions <7.15.2-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.66% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-OAUTH2PROXYADVANCEDCOMPAT-16087905
  • published16 Apr 2026
  • disclosed14 Apr 2026
Report a new vulnerability Found a mistake?

Introduced: 14 Apr 2026

CVE-2026-34457  (opens in a new tab)
CWE-290  (opens in a new tab)

How to fix?

Upgrade Minimos:latest oauth2-proxy-advanced-compat to version 7.15.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream oauth2-proxy-advanced-compat package and not the oauth2-proxy-advanced-compat package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.