Skip to main content

OAuth2 Proxy CVE-2026-41059

HIGH
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-04-21 GitHub_M GHSA-pxq7-h93f-9jrg
8.2
CVSS 3.1 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
SUSE
HIGH
qualitative
Red Hat
7.5 MEDIUM
qualitative

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

Lifecycle Timeline

4
Re-analysis Queued
Apr 22, 2026 - 21:37 vuln.today
cvss_changed
Analysis Generated
Apr 22, 2026 - 00:57 vuln.today
Analysis Generated
Apr 21, 2026 - 23:31 vuln.today
CVE Published
Apr 21, 2026 - 23:17 nvd
HIGH 8.2

DescriptionGitHub Advisory

OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 have a configuration-dependent authentication bypass. Deployments are affected when all of the following are true: Use of skip_auth_routes or the legacy skip_auth_regex; use of patterns that can be widened by attacker-controlled suffixes, such as ^/foo/.*/bar$ causing potential exposure of /foo/secret; and protected upstream applications that interpret # as a fragment delimiter or otherwise route the request to the protected base path. In deployments that rely on these settings, an unauthenticated attacker can send a crafted request containing a number sign in the path, including the browser-safe encoded form %23, so that OAuth2 Proxy matches a public allowlist rule while the backend serves a protected resource. Deployments that do not use these skip-auth options, or that only allow exact public paths with tightly scoped method and path rules, are not affected. A fix has been implemented in version 7.15.2 to normalize request paths more conservatively before skip-auth matching so fragment content does not influence allowlist decisions. Users who cannot upgrade immediately can reduce exposure by tightening or removing skip_auth_routes and skip_auth_regex rules, especially patterns that use broad wildcards across path segments. Recommended mitigations include replacing broad rules with exact, anchored public paths and explicit HTTP methods; rejecting requests whose path contains %23 or # at the ingress, load balancer, or WAF level; and/or avoiding placing sensitive application paths behind broad skip_auth_routes rules.

AnalysisAI

Authentication bypass in OAuth2 Proxy 7.5.0-7.15.1 allows remote unauthenticated attackers to access protected resources by exploiting path normalization discrepancies between the proxy and backend services. When deployments use skip_auth_routes or skip_auth_regex with broad wildcard patterns, attackers can inject '#' or '%23' (URL-encoded fragment delimiter) to match public allowlist rules while the upstream application serves sensitive endpoints. CVSS 8.2 (AV:N/AC:L/PR:N/UI:N) reflects network-based unauthenticated access; no public exploit identified at time of analysis. EPSS data not provided. Fixed in version 7.15.2 through conservative path normalization.

Technical ContextAI

OAuth2 Proxy functions as a reverse proxy enforcing authentication via OAuth2/OIDC providers before forwarding requests to upstream applications. The vulnerability (CWE-288: Authentication Bypass Using an Alternate Path or Channel) stems from inconsistent interpretation of URI fragments between OAuth2 Proxy's skip-auth pattern matching logic and backend HTTP servers. Per CPE cpe:2.3:a:oauth2-proxy:oauth2-proxy:*:*:*:*:*:*:*:*, all OAuth2 Proxy versions 7.5.0-7.15.1 are affected. The flaw occurs when skip_auth_routes or skip_auth_regex uses regular expressions with wildcards spanning path segments (e.g., ^/foo/.*/bar$) that inadvertently permit attacker-controlled fragments. HTTP backends treating '#' as a fragment delimiter (per RFC 3986) or applying routing normalization can resolve crafted paths like /foo/secret#/bar to protected resources while OAuth2 Proxy incorrectly matches the literal string against public allowlist patterns. The fix in 7.15.2 normalizes request paths before skip-auth evaluation, stripping fragment components to ensure routing consistency.

RemediationAI

Vendor-released patch: OAuth2 Proxy 7.15.2 implements conservative path normalization stripping fragment content before skip-auth rule evaluation. Upgrade immediately via package manager or container image update; verify using oauth2-proxy --version. For deployments unable to upgrade, apply defense-in-depth mitigations in priority order: (1) Replace broad skip_auth_routes patterns like ^/public/.*/assets$ with exact anchored paths (^/public/css$, ^/public/js$) and explicit HTTP methods (GET only for static assets); (2) Deploy WAF or ingress controller rules rejecting requests containing '#' or '%23' in URI paths-note this may break legitimate applications using fragment identifiers in server-side routing, test thoroughly in staging; (3) Audit backend application routing to confirm fragment-handling behavior, reconfigure applications to reject fragment-containing paths if possible; (4) Remove skip_auth_regex entirely if legacy feature, migrate to skip_auth_routes with method-scoped rules. Consult GitHub advisory https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-pxq7-h93f-9jrg for additional hardening guidance. Each workaround trades operational flexibility for security-exact-path whitelisting increases configuration overhead, fragment rejection may break edge-case applications.

CVE-2021-21291 MEDIUM POC
6.1 Feb 02

OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google

CVE-2020-5233 MEDIUM POC
6.1 Jan 30

OAuth2 Proxy before 5.0 has an open redirect vulnerability. Rated medium severity (CVSS 6.1), this vulnerability is remo

CVE-2026-76835 CRITICAL POC
9.3 Aug 24

Authentication bypass in OAuth2 Proxy (versions 7.5.0 up to but excluding 7.15.2) lets an unauthenticated remote attacke

CVE-2026-34457 CRITICAL
9.1 Apr 14

Authentication bypass in OAuth2 Proxy versions before 7.15.2 allows remote unauthenticated attackers to access protected

CVE-2017-1000069 HIGH
8.8 Jul 17

CSRF in Bitly oauth2_proxy 2.1 during authentication flow. Rated high severity (CVSS 8.8), this vulnerability is remotel

CVE-2017-1000070 MEDIUM
6.1 Jul 17

The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and te

CVE-2020-11053 MEDIUM
6.1 May 07

In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. Rated medium severity (CVSS 6.1), this vulnerabil

CVE-2021-21411 MEDIUM
5.5 Mar 26

OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. Rated

CVE-2020-4037 MEDIUM
5.4 Jun 29

In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address for the proxy to se

CVE-2026-34454 LOW
3.5 Apr 14

OAuth2 Proxy versions 7.11.0 through 7.15.1 fail to clear the session cookie when rendering the sign-in page due to a re

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP5 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP6 Affected
openSUSE Leap 15.5 Affected

Share

CVE-2026-41059 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy