EUVD-2026-22761
GHSA-5hvv-m4w4-gf6v
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
6DescriptionCVE.org
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.
AnalysisAI
Authentication bypass in OAuth2 Proxy versions before 7.15.2 allows remote unauthenticated attackers to access protected resources when deployed with nginx auth_request integration and health check features enabled. Attackers can spoof health check User-Agent headers to bypass OAuth2 authentication entirely, gaining unauthorized access to upstream applications. CVSS 9.1 (Critical) reflects network-accessible, low-complexity attack requiring no privileges or user interaction. No active exploitation confirmed (not in CISA KEV), but the trivial attack complexity and authentication bypass impact warrant immediate patching in affected deployments using nginx auth_request with --ping-user-agent or --gcp-healthchecks flags.
Technical ContextAI
OAuth2 Proxy is a reverse proxy that enforces OAuth2 authentication before forwarding requests to upstream services. In nginx deployments, the auth_request directive creates subrequests to OAuth2 Proxy to validate authentication before serving protected content. The vulnerability (CWE-290: Authentication Bypass by Spoofing) stems from improper health check request validation. When --ping-user-agent or --gcp-healthchecks is configured, OAuth2 Proxy is intended to respond successfully to health monitoring probes matching specific User-Agent strings. However, affected versions fail to restrict this health check logic to designated health check endpoints, treating ANY request with the configured health check User-Agent as valid regardless of the requested path. This allows attackers to craft HTTP requests with spoofed User-Agent headers to bypass authentication checks entirely, as the proxy returns successful authentication responses to nginx for what should be protected resources. The flaw only manifests in auth_request-style integrations where the proxy's response directly determines access control decisions.
RemediationAI
Immediately upgrade OAuth2 Proxy to version 7.15.2 or later, which contains fixes for the authentication bypass vulnerability. The patched release is available at https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.15.2 with complete remediation for the health check validation flaw. Organizations unable to upgrade immediately should disable --ping-user-agent and --gcp-healthchecks configuration flags as a temporary mitigation, though this impacts health monitoring capabilities. Alternative interim mitigation involves restricting health check endpoints at the nginx level to specific paths and removing auth_request directives from those locations, ensuring health checks do not bypass authentication validation for protected resources. Review nginx configuration to ensure auth_request integration properly isolates health check endpoints from application paths. Consult the GitHub security advisory at https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-5hvv-m4w4-gf6v for deployment-specific guidance and configuration validation steps.
More in Oauth2 Proxy
View allOAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google
OAuth2 Proxy before 5.0 has an open redirect vulnerability. Rated medium severity (CVSS 6.1), this vulnerability is remo
Authentication bypass in OAuth2 Proxy (versions 7.5.0 up to but excluding 7.15.2) lets an unauthenticated remote attacke
CSRF in Bitly oauth2_proxy 2.1 during authentication flow. Rated high severity (CVSS 8.8), this vulnerability is remotel
Authentication bypass in OAuth2 Proxy 7.5.0-7.15.1 allows remote unauthenticated attackers to access protected resources
The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and te
In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. Rated medium severity (CVSS 6.1), this vulnerabil
OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. Rated
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 se
OAuth2 Proxy versions 7.11.0 through 7.15.1 fail to clear the session cookie when rendering the sign-in page due to a re
Same weakness CWE-290 – Authentication Bypass by Spoofing
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today