Vulnerabilities / CVE-2026-34457

critical

CVE-2026-34457

OAuth2 Proxy's Health Check User-Agent Matching Bypasses Authentication in auth_request Mode

Published Modified CWE 290
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Bitnami9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Trivy's own label is CRITICAL. Rated critical by GHSA, Bitnami.

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.

Affected packages and fixed versions

SourcePackageFixed in
bitnami::Bitnami Vulnerability Databaseoauth2-proxy7.15.2
go::GitHub Security Advisory Gogithub.com/oauth2-proxy/oauth2-proxy, github.com/oauth2-proxy/oauth2-proxy/v77.15.2
minimosoauth2-proxy, oauth2-proxy-fips7.15.2-r0
Show all 5 entries from 3 sources
SourcePackageFixed in
bitnami::Bitnami Vulnerability Databaseoauth2-proxy7.15.2
go::GitHub Security Advisory Gogithub.com/oauth2-proxy/oauth2-proxyno fix listed
go::GitHub Security Advisory Gogithub.com/oauth2-proxy/oauth2-proxy/v77.15.2
minimosoauth2-proxy7.15.2-r0
minimosoauth2-proxy-fips7.15.2-r0

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.