github.com/oauth2-proxy/oauth2-proxy/v7
Affected
- introduced
7.5.0, fixed7.15.2(semver)
Fixed versions
7.15.2
Fix
- Fixed version
7.15.2go get github.com/oauth2-proxy/oauth2-proxy/[email protected]
Advisory
Also known as: BIT-oauth2-proxy-2026-40575, BIT-oauth2-proxy-2026-76835, CVE-2026-40575, CVE-2026-76835, GO-2026-5236
OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
Impact
A configuration-dependent authentication bypass exists in OAuth2 Proxy.
Deployments are affected when all of the following are true:
--reverse-proxy--skip_auth_routes or the legacy --skip-auth-regexOAuth2 Proxy may trust a client-supplied X-Forwarded-Uri header when --reverse-proxy is enabled and --skip-auth-route or --skip-auth-regex is configured. An attacker can spoof this header so OAuth2 Proxy evaluates authentication and skip-auth rules against a different path than the one actually sent to the upstream application.
This can result in an unauthenticated remote attacker bypassing authentication and accessing protected routes without a valid session.
Patches
This issue is addressed as part of the newly introduced --trusted-proxy-ip flag in v7.15.2. If you leave it unset, OAuth2 Proxy will continue to trust ALL source IPs (0.0.0.0/0) for backwards compatibility, which means a client may still be able to spoof forwarded headers. Therefore after upgrading we urge you to use the new --trusted-proxy-ip flag to set the IPs or CIDR ranges of the reverse proxies that are allowed to send X-Forwarded-* headers and furthermore implement the mitigation steps outlined below to properly configure your load balancer infrastructure.
Mitigation
X-Forwarded-Uri header at the reverse proxy or load balancer levelX-Forwarded-Uri with the actual request URI before forwarding requests to OAuth2 ProxyExample nginx mitigation for the auth subrequest:
location /internal-auth/ {
internal; # Ensure external users can't access this path
# Make sure the OAuth2 Proxy knows where the original request came from.
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
# set the value to the actual $request_uri and therefore strip any user provided X-Forwarded-Uri
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_pass http://oauth2-proxy:4180/;
}
--skip-auth-route / --skip-auth-regex rules where possibleCritical Basis: The source's own band: CRITICAL
7.5.0, fixed 7.15.2 (semver)7.15.2
7.15.2go 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