github.com/oauth2-proxy/oauth2-proxy/v7
Affected
- introduced
0, fixed7.15.2(semver)
Fixed versions
7.15.2
Fix
- Fixed version
7.15.2go get github.com/oauth2-proxy/oauth2-proxy/[email protected]
Advisory
Also known as: BIT-oauth2-proxy-2026-40574, CVE-2026-40574, GO-2026-5314
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.
Medium Basis: The source's own band: MODERATE
0, fixed 7.15.2 (semver)7.15.2
7.15.2go get github.com/oauth2-proxy/oauth2-proxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0