# CVE-2025-54576: OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion

Source: https://junglewise.ai/threats/cve-2025-54576-oauth2-proxy-has-authentication-bypass-in-oauth2-proxy-skip-auth  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-08-11  
License: CC BY 4.0 with a link back

CVE-2025-54576 · Severity: low · CVSS 3.1 · Published 2025-08-11

OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion in github.com/oauth2-proxy/oauth2-proxy

Technologies: [github.com/oauth2-proxy/oauth2-proxy (Go)](https://junglewise.ai/threats/technologies/github-com-oauth2-proxy-oauth2-proxy), [github.com/oauth2-proxy/oauth2-proxy/v7 (Go)](https://junglewise.ai/threats/technologies/github-com-oauth2-proxy-oauth2-proxy-v7). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-54576 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-54576 being exploited in the wild.

**How severe is CVE-2025-54576?** Low severity, with a CVSS score of 3.1, published 11 August 2025.

**Which products and versions are affected?** github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0; github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.11.0.

**Is there a fix for CVE-2025-54576?** Yes. github.com/oauth2-proxy/oauth2-proxy/v7 (Go): upgrade to 7.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-54576?** Check whether you run github.com/oauth2-proxy/oauth2-proxy (Go) or github.com/oauth2-proxy/oauth2-proxy/v7 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/oauth2-proxy/oauth2-proxy/v7 (Go): upgrade to 7.11.0 or later

  ```sh
  go get github.com/oauth2-proxy/oauth2-proxy/v7@v7.11.0
  ```


## Affected products

- github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0
- github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.11.0

## Identifiers

- CVE-2025-54576
- GHSA-7rh7-c77v-6434
- GO-2025-3833

## Related threats

- [OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex](https://junglewise.ai/threats/cve-2026-41059-oauth2-proxy-has-an-authentication-bypass-via-fragment-confusion)
- [OAuth2 Proxy authentication bypass via X-Forwarded-Uri spoofing](https://junglewise.ai/threats/cve-2026-40575-oauth2-proxy-authentication-bypass-via-x-forwarded-uri-spoofing)
- [OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims](https://junglewise.ai/threats/cve-2026-40574-oauth2-proxy-has-an-authorization-bypass-in-email-domain)
- [OAuth2 Proxy authentication bypass via health check User-Agent spoofing](https://junglewise.ai/threats/cve-2026-34457-oauth2-proxy-authentication-bypass-via-health-check-user-agent)
- [OAuth2 Proxy insufficient session expiration in sign-in page handler](https://junglewise.ai/threats/cve-2026-34454-oauth2-proxy-insufficient-session-expiration-in-sign-in-page)