CVE-2026-34457 json
OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
published 2026-04-14 6 mo ago modified 2026-09-08 2 mo ago also BIT-oauth2-proxy-2026-34457 , EUVD-2026-22761 , GHSA-5hvv-m4w4-gf6v , GO-2026-5147
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/oauth2-proxy/oauth2-proxy/v7 7.15.2
- bitnami oauth2-proxy 7.15.2
- oauth2_proxy_project oauth2_proxy 7.15.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 6 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/oauth2-proxy/oauth2-proxy/v7 | <7.15.2 |
7.15.2 |
| go | github.com/oauth2-proxy/oauth2-proxy | <=3.2.0 all versions |
no fix listed |
| bitnami | oauth2-proxy | <7.15.2 |
7.15.2 |
Affected products
- oauth2-proxy oauth2-proxy
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
github.com
/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-5hvv-m4w4-gf6v
web, mitigation, vendor-advisory, advisory
-
github.com
/oauth2-proxy/oauth2-proxy/releases/tag/v7.15.2
web, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-34457
advisory, web
-
github.com
/oauth2-proxy/oauth2-proxy
package
Sources
- CVE List CVE-2026-34457
- GitHub Advisory GHSA-5hvv-m4w4-gf6v
- NVD CVE-2026-34457
- OSV BIT-oauth2-proxy-2026-34457
- OSV GO-2026-5147
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.