Skip to content

CVE-2026-34457

Oauth2 Proxy Project Oauth2 Proxy authentication bypass

9.1 CRITICALEPSS 0.66%
  1. Published14 Apr 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Oauth2 Proxy Project Oauth2 Proxy< 7.15.2

Remediation

Fixed in
Oauth2 Proxy Project Oauth2 Proxy≥ 7.15.2

Frequently asked

Is CVE-2026-34457 being actively exploited?

CVE-2026-34457 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.66%.

How severe is CVE-2026-34457?

CVE-2026-34457 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.66% probability of exploitation.

Which products are affected by CVE-2026-34457?

Affected products include Oauth2 Proxy Project Oauth2 Proxy.

How do I fix CVE-2026-34457?

Upgrade affected software to a fixed version, for example Oauth2 Proxy Project Oauth2 Proxy 7.15.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-34457 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.