github.com/oauth2-proxy/oauth2-proxy/v7
Affected
- introduced
0, fixed7.11.0(semver)
Fixed versions
7.11.0
Fix
- Fixed version
7.11.0go get github.com/oauth2-proxy/oauth2-proxy/[email protected]
Advisory
Also known as: BIT-oauth2-proxy-2025-54576, CVE-2025-54576, GO-2025-3833
OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion
Impact
This vulnerability affects oauth2-proxy deployments using the skip_auth_routes configuration option with regex patterns. The vulnerability allows attackers to bypass authentication by crafting URLs with query parameters that satisfy the configured regex patterns, potentially gaining unauthorized access to protected resources.
The issue stems from skip_auth_routes matching against the full request URI (path + query parameters) instead of just the path as documented. This discrepancy enables authentication bypass attacks where attackers append malicious query parameters to access protected endpoints.
Example Attack:
skip_auth_routes = [ "^/foo/.*/bar$" ]/foo/something/bar/foo/critical_endpoint?param=/barDeployments using skip_auth_routes with regex patterns containing wildcards or broad matching patterns are most at risk, especially when backend services ignore unknown query parameters.
Patches
A patch has been released with version v7.11.0.
Workarounds
Immediate mitigations:
skip_auth_routes configurations for overly permissive patterns^ and end with $)Example secure configuration:
# Instead of: "^/public/.*"
# Use specific paths: "^/public/assets$", "^/public/health$"
skip_auth_routes = ["^/public/assets$", "^/public/health$", "^/api/status$"]Critical Basis: The source's own band: CRITICAL
0, fixed 7.11.0 (semver)7.11.0
7.11.0go get github.com/oauth2-proxy/oauth2-proxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0