CVE-2026-40575 is a critical authentication bypass vulnerability affecting OAuth2 Proxy versions 7.5.0 through 7.15.1. When the reverse proxy mode is enabled alongside skip-auth rules, the application improperly trusts the client-supplied X-Forwarded-Uri header, allowing attackers to spoof this header and bypass authentication checks by manipulating which path OAuth2 Proxy evaluates against its security rules. This vulnerability specifically impacts deployments using the --reverse-proxy flag in combination with --skip-auth-regex or --skip-auth-route configurations. The vulnerability carries a CVSS score of 9.1 (Critical) with an attack vector that is network-based, requires no authentication or user interaction, and presents no special access complexity. The impact is severe, with attackers able to achieve high confidentiality and integrity compromise by gaining unauthorized access to protected routes and sensitive data without valid authentication sessions. The attack requires only standard HTTP manipulation capabilities available to remote, unauthenticated threat actors. Exploitation status indicates this vulnerability is not currently listed on the Known Exploited Vulnerabilities (KEV) catalog and remains inactive on security hot lists, suggesting limited active exploitation in the wild at this time. However, the straightforward nature of the attack—requiring only header manipulation—combined with the high CVSS severity means organizations should treat this as a priority for patching. The vulnerability is patched in version 7.15.2, and multiple workarounds exist for organizations unable to upgrade immediately, including header stripping at the reverse proxy layer and restricting direct client access to OAuth2 Proxy.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
>= 7.5.0, < 7.15.2CPE matchmatch criteria | cpe:2.3:a:oauth2_proxy_project:oauth2_proxy:*:*:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.3 Bluesky, 0.3 Mastodon, and 2.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.3 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.