CVE-2025-54576 OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion
Attackers can bypass authentication in OAuth2-Proxy by crafting URLs with query parameters that match skip_auth_routes regex patterns, gaining unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-54576?
CVE-2025-54576 is a critical authentication bypass vulnerability in oauth2-proxy, published on 30 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. In versions 7.10.0 and below, oauth2-proxy deployments are vulnerable when using the skip_auth_routes configuration option with regex patterns. Attackers can bypass authentication by crafting URLs with query parameters that satisfy configured regex patterns, allowing unauthorized access to protected resources. The issue stems from skip_auth_routes matching against the full request URI. Deployments using skip_auth_routes with regex patterns containing wildcards or broad matching patterns are most at risk. This issue is fixed in version 7.11.0. Workarounds include: auditing all skip_auth_routes configurations for overly permissive patterns, replacing wildcard patterns with exact path matches where possible, ensuring regex patterns are properly anchored (starting with ^ and ending with $), or implementing custom validation that strips query parameters before regex matching.
Weakness: CWE-290
Which versions are affected by CVE-2025-54576?
5 open source packages ship an affected version, including github.com/oauth2-proxy/oauth2-proxy/v7, oauth2-proxy and github.com/oauth2-proxy/oauth2-proxy. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/oauth2-proxy/oauth2-proxy/v7 Go | All versions | 7.11.0 |
github.com/oauth2-proxy/oauth2-proxy/v7 Go | All versions | 7.11.0 |
github.com/oauth2-proxy/oauth2-proxy/v7 Go | All versions | 7.11.0 |
oauth2-proxy Bitnami | All versions | 7.11.0 |
github.com/oauth2-proxy/oauth2-proxy Go | All versions | None |
Products include Oauth2 Proxy Project Oauth2 Proxy.
How do I fix CVE-2025-54576?
Upgrade github.com/oauth2-proxy/oauth2-proxy/v7 to 7.11.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-54576 being exploited?
There is no known exploitation of CVE-2025-54576 in the wild and no public exploit code.
Other vulnerabilities in oauth2-proxy
- CVE-2026-40575 OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
- CVE-2026-34457 OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
- CVE-2017-1000069 Cross-site Request Forgery (CSRF)
- CVE-2026-41059 OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
- CVE-2020-11053 Open Redirect in OAuth2 Proxy
Sources
Also known as BIT-oauth2-proxy-2025-54576, GHSA-7rh7-c77v-6434, GO-2025-3833.