CVE-2026-34457

CVE-2026-34457 is a critical-severity vulnerability in Oauth2 Proxy Project Oauth2 Proxy with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-290.

Key facts

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.

Frequently asked questions

What is CVE-2026-34457?
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 severe is CVE-2026-34457?
CVE-2026-34457 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-34457 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-34457?
CVE-2026-34457 affects Oauth2 Proxy Project Oauth2 Proxy. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-34457?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-34457 have an EU (EUVD) identifier?
Yes. CVE-2026-34457 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-22761.
When was CVE-2026-34457 published?
CVE-2026-34457 was published on 2026-04-14 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Oauth2 Proxy Project Oauth2 Proxy

All CVEs affecting Oauth2 Proxy Project Oauth2 Proxy →

Other CWE-290 vulnerabilities

Browse all CWE-290 vulnerabilities →