CVE-2026-41059: oauth2-proxy · Authentication Bypass Using an Alternate Path or Channel
Affects oauth2-proxySource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 7.15.2 soon.
Data as of 12 Nov 2026, 01:32 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
- Patch
- Available – fixed in 7.15.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade oauth2-proxy to 7.15.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| oauth2-proxy oauth2-proxy | Affected
| Fixed in
|
AI-suggested
A fix is available in oauth2-proxy version 7.15.2, which should be applied to resolve this vulnerability. Users unable to upgrade immediately should tighten or remove skip_auth_routes and skip_auth_regex rules, especially avoiding broad wildcard patterns across path segments. Recommended mitigations include replacing broad rules with exact, anchored public paths and explicit HTTP methods; rejecting requests containing %23 or # at ingress, load balancer, or WAF levels; and avoiding placing sensitive application paths behind broad skip-auth rules.
Description
OAuth2 Proxy versions 7.5.0 through 7.15.1 have a configuration-dependent authentication bypass vulnerability. This occurs when certain skip-authentication route patterns are used that can be manipulated by attackers using a number sign (#) or its encoded form (%23) in the request path. This allows unauthenticated access to protected resources if the backend interprets the fragment delimiter in a way that bypasses OAuth2 Proxy's authentication checks. The issue is fixed in version 7.15.2 by normalizing request paths before matching skip-auth rules.