Bug 2385267 (CVE-2025-54576) - CVE-2025-54576 github.com/oauth2-proxy/oauth2-proxy: OAuth2-Proxy authentication bypass
Summary: CVE-2025-54576 github.com/oauth2-proxy/oauth2-proxy: OAuth2-Proxy authenticat...
Keywords:
Status: NEW
Alias: CVE-2025-54576
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2385282
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-30 20:01 UTC by OSIDB Bzimport
Modified: 2025-07-31 14:06 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-07-30 20:01:08 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.