CVE-2026-34457
Auth bypass in OAuth2 Proxy <7.15.2 with auth_request/health checks.
Is CVE-2026-34457 being exploited?
Not confirmed. CVE-2026-34457 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-34457?
CVE-2026-34457 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34457?
Yes. A fix has been recorded for CVE-2026-34457. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34457 affect?
CVE-2026-34457 affects OAuth2 Proxy <7.15.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34457?
Upgrade to 7.15.2+; review --ping-user-agent/--gcp-healthchecks usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated bypass allows access to protected upstream resources via health-check User-Agent.
Immediate action required
- affected< 7.15.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.