CVE-2026-40574: OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims

Published Apr 15, 2026
·
Updated

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 attacker@evil.com@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 emaildomain 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.

Other sources

OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Prior to 7.15.2, 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 attacker@evil.com@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 emaildomain restrictions and accept email claim values from identity providers or claim mappings that do not strictly enforce normal email syntax. This vulnerability is fixed in 7.15.2.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/oauth2-proxy/oauth2-proxy/v7<7.15.2
7.15.2
Oauth2 Proxy Project Oauth2 Proxy<7.15.2

Event History

Apr 15, 2026
Advisory Published
via GitHub·07:23 PM
Data Sourced
via GitHub·07:23 PM
DescriptionSeverityWeaknessAffected Software
Apr 21, 2026
CVE Published
via MITRE·04:32 PM
Data Sourced
via MITRE·04:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40574?

CVE-2026-40574 has a high severity due to the potential for unauthorized access through an email domain bypass.

2

How do I fix CVE-2026-40574?

To fix CVE-2026-40574, upgrade to OAuth2 Proxy version 7.15.2 or later.

3

What is the attack vector for CVE-2026-40574?

The attack vector for CVE-2026-40574 involves an attacker impersonating a user by exploiting the email domain enforcement option.

4

What impact does CVE-2026-40574 have on applications?

CVE-2026-40574 can allow unauthorized users to authenticate and gain access to sensitive resources.

5

What is the affected software for CVE-2026-40574?

The affected software for CVE-2026-40574 is the OAuth2 Proxy, specifically versions prior to 7.15.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203