CVE-2026-34457
- Source
- https://cve.org/CVERecord?id=CVE-2026-34457
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-34457.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-34457
- Aliases
- Downstream
- Published
- 2026-04-14T22:14:38.937Z
- Modified
- 2026-07-08T08:13:43.248382795Z
- Severity
-
- 9.1 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
- Details
-
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 authrequest-style integration (such as nginx authrequest) 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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34457.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-290" ] }- References
Affected packages
Git / github.com/oauth2-proxy/oauth2-proxy
Affected ranges
- Type
- GIT
- Repo
- https://github.com/oauth2-proxy/oauth2-proxy
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "source": [ "AFFECTED_FIELD", "CPE_RANGE", "REFERENCES" ], "cpe": "cpe:2.3:a:oauth2_proxy_project:oauth2_proxy:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "7.15.2" } ] }