CVE-2026-40574: oauth2-proxy · Incorrect Authorization
Affects oauth2-proxySource GCVE Database
Not known to be exploited · CVSS 6.8 Medium : upgrade to 7.15.2 when convenient.
Data as of 12 Nov 2026, 01:33 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.8 |
|---|
- Patch
- Available – fixed in 7.15.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade oauth2-proxy to 7.15.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| oauth2-proxy oauth2-proxy | Affected
| Fixed in
|
AI-suggested
Upgrade OAuth2 Proxy to version 7.15.2 or later, where this vulnerability is fixed. Deployments relying on email_domain restrictions should ensure that identity providers or claim mappings strictly enforce valid email syntax to prevent bypass. No other mitigation is required once the upgrade is applied.
Description
OAuth2 Proxy versions prior to 7.15.2 contain an authorization bypass vulnerability related to the email_domain enforcement option. An attacker can exploit this by using crafted email claims like attacker@evil.com@company.com to bypass domain restrictions. This affects deployments relying on email_domain restrictions that accept email claims without strict email syntax enforcement. The vulnerability is fixed in version 7.15.2.