CVE-2026-40574: OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims
Impact An authorization bypass exists in OAuth2 Proxy as part of the emaildomain enforcement option. An attacker may be able to authenticate with an email claim such as [email protected]@company.com and satisfy an allowed domain check for company.com, even though the claim is not a valid email address.
Published Apr 15, 2026 · Updated Apr 27, 2026
Affected packages
github.com/oauth2-proxy/oauth2-proxy/v7
- Ecosystem
- Go
- Affected
- < 7.15.2
- Fixed in
- 7.15.2
- Check
go list -m github.com/oauth2-proxy/oauth2-proxy/v7
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An authorization bypass exists in OAuth2 Proxy as part of the email_domain enforcement option. An attacker may be able to authenticate with an email claim such as [email protected]@company.com and satisfy an allowed domain check for company.com, even though the claim is not a valid email address.
The issue ONLY affects deployments that rely on email_domain restrictions and accept email claim values from identity providers or claim mappings that do not strictly enforce normal email syntax. The practical risk ONLY exists in self-hosted or custom OIDC environments and federated setups where unexpected claim values can reach oauth2-proxy. Standard hosted providers that enforce valid email formatting ARE NOT effected.
Patches
Users should upgrade to v7.15.2 or later once available.
Workarounds
The most effective workaround is to ensure the configured identity provider cannot emit malformed or attacker-controlled email claim values.
Credited to kodareef5.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-40575
OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
critical9.1Apr 15, 2026CVE-2026-41059
OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
high8.2Apr 15, 2026CVE-2026-34454
OAuth2 Proxy's session cookies are not cleared when rendering sign-in page
low3.5Apr 14, 2026CVE-2026-34457
OAuth2 Proxy's Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
critical9.1No fixApr 14, 2026CVE-2025-64484
OAuth2-Proxy is vulnerable to header smuggling via underscore leading to potential privilege escalation
high8.5Nov 12, 2025CVE-2021-21411
OAuth2-Proxy's `--gitlab-group` GitLab Group Authorization config flag stopped working in v7.0.0
medium5.5Jul 30, 2025
