Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-40575— OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing

CVSS 9.1 · Critical EPSS 0.11% · P29
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-40575

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
Source: NVD (National Vulnerability Database)
Vulnerability Description
OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions 7.5.0 through 7.15.1 may trust a client-supplied `X-Forwarded-Uri` header when `--reverse-proxy` is enabled and `--skip-auth-regex` or `--skip-auth-route` is configured. An attacker can spoof this header so OAuth2 Proxy evaluates authentication and skip-auth rules against a different path than the one actually sent to the upstream application. This can result in an unauthenticated remote attacker bypassing authentication and accessing protected routes without a valid session. Impacted users are deployments that run oauth2-proxy with `--reverse-proxy` enabled and configure at least one `--skip-auth-regex` or `--skip-auth-route` rule. This issue is patched in `v7.15.2`. Some workarounds are available for those who cannot upgrade immediately. Strip any client-provided `X-Forwarded-Uri` header at the reverse proxy or load balancer level; explicitly overwrite `X-Forwarded-Uri` with the actual request URI before forwarding requests to OAuth2 Proxy; restrict direct client access to OAuth2 Proxy so it can only be reached through a trusted reverse proxy; and/or remove or narrow `--skip-auth-regex` / `--skip-auth-route` rules where possible. For nginx-based deployments, ensure `X-Forwarded-Uri` is set by nginx and not passed through from the client.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source: NVD (National Vulnerability Database)
Vulnerability Type
使用欺骗进行的认证绕过
Source: NVD (National Vulnerability Database)
Vulnerability Title
OAuth2 Proxy 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
OAuth2 Proxy是OAuth2 Proxy组织的一款能够提供与Google、Github或其他提供商进行身份验证的反向代理。 OAuth2 Proxy 7.5.0版本至7.15.1版本存在安全漏洞,该漏洞源于当启用反向代理并配置跳过身份验证规则时,可能信任客户端提供的X-Forwarded-Uri标头,可能导致未经身份验证的远程攻击者绕过身份验证并访问受保护路由。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Shenlong Deep Dive — AI Deep Analysis

10-question deep dive: root cause, exploitation, mitigation, urgency. Read summary free, full version requires login.

Affected Products

VendorProductAffected VersionsCPESubscribe
oauth2-proxyoauth2-proxy >= 7.5.0, < 7.15.2 -

II. Public POCs for CVE-2026-40575

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-40575

登录查看更多情报信息。

Same Patch Batch · oauth2-proxy · 2026-04-21 · 3 CVEs total

CVE-2026-410598.2 HIGHOAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and s
CVE-2026-405746.8 MEDIUMOAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@

IV. Related Vulnerabilities

V. Comments for CVE-2026-40575

No comments yet


Leave a comment