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

Advisory record · `GHSA-5hvv-m4w4-gf6v`

- **Identifiers:** `GHSA-5hvv-m4w4-gf6v` · `BIT-oauth2-proxy-2026-34457` · `CVE-2026-34457` · `GO-2026-5147`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-290](https://cwe.mitre.org/data/definitions/290.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 14 Apr 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Apr 2026, 22:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/oauth2-proxy/oauth2-proxy/v7` (Go): affected `<7.15.2`; fixed in `7.15.2`
- `github.com/oauth2-proxy/oauth2-proxy` (Go): affected `<=3.2.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of oauth2-proxy v7 before 7.15.2 are affected when used with auth_request-style integration and either --ping-user-agent or --gcp-healthchecks enabled. An unauthenticated remote attacker can send a request with the configured health check User-Agent to bypass authentication and reach protected upstream resources. Upgrade to 7.15.2 or later. Alternatively, disable --gcp-healthchecks, remove --ping-user-agent, or stop the reverse proxy from forwarding client-supplied User-Agent headers to the auth subrequest.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 43rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5hvv-m4w4-gf6v)

## Sources

- [GitHub Advisory Database: GHSA-5hvv-m4w4-gf6v](https://github.com/advisories/GHSA-5hvv-m4w4-gf6v)
- [OSV: GHSA-5hvv-m4w4-gf6v](https://osv.dev/vulnerability/GHSA-5hvv-m4w4-gf6v)
- <https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-5hvv-m4w4-gf6v>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34457>
- <https://github.com/oauth2-proxy/oauth2-proxy>
- <https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.15.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5hvv-m4w4-gf6v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5hvv-m4w4-gf6v/>. Everything for agents: <https://agentprime.io/llms.txt>.
