{"id":"CVE-2026-41059","summary":"OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex","details":"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.","aliases":["BIT-oauth2-proxy-2026-41059","GHSA-pxq7-h93f-9jrg","GO-2026-5559"],"modified":"2026-08-12T03:51:44.364906028Z","published":"2026-04-21T23:17:46.743Z","related":["openSUSE-SU-2026:21483-1"],"database_specific":{"cwe_ids":["CWE-288"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41059.json","cna_assigner":"GitHub_M"},"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41059.json"},{"type":"ADVISORY","url":"https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-pxq7-h93f-9jrg"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-41059"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/oauth2-proxy/oauth2-proxy","events":[{"introduced":"01386bf30348f75590df61a3408187696fef6d4b"},{"fixed":"5961fd99b42c3625b8ef08690d38be5cb37f44b0"}],"database_specific":{"source":["AFFECTED_FIELD","CPE_RANGE"],"cpe":"cpe:2.3:a:oauth2_proxy_project:oauth2_proxy:*:*:*:*:*:*:*:*","extracted_events":[{"introduced":"7.5.0"},{"fixed":"7.15.2"}]}}],"versions":["v7.15.1","v7.15.0","v7.14.3","v7.14.2","v7.14.1","v7.14.0","v7.13.0","v7.12.0","v7.11.0","v7.10.0","v7.9.0","v7.8.2","v7.8.1","v7.8.0","v7.7.1","v7.7.0","v7.6.0","v7.5.1","v7.5.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-41059.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"}]}