🛡️ CVE-2026-40574 — oauth2-proxy
Description
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 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.
Affected software
CVE-2026-40574 is recorded against 3 packages.
- github.com/oauth2-proxy/oauth2-proxy
- github.com/oauth2-proxy/oauth2-proxy/v7
- oauth2-proxy
Timeline and source
Published on 25 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| github.com/oauth2-proxy/oauth2-proxy | — | — |
| github.com/oauth2-proxy/oauth2-proxy/v7 | — | — |
| oauth2-proxy | — | — |
References
Similar Threats
- High CVE-2026-41059
- Critical CVE-2026-40575
- Low CVE-2026-34454
- Critical CVE-2026-34457
- High CVE-2025-64484
Vulnerability Monitoring
Track new vulnerabilities in oauth2-proxy
CVE-2026-40574 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.