Skip to main content
VulnerabilityPublished

CVE-2026-40574: oauth2-proxy · Incorrect Authorization

Affects oauth2-proxySource GCVE Database

0
Compare

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

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
oauth2-proxy oauth2-proxyAffected
  • <7.15.2
Fixed in
  • 7.15.2

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.

References

Community reviews

Loading reviews…