Skip to content
Authentication Bypass in OAuth2 Proxy Vulnerability Disclosed

Authentication Bypass in OAuth2 Proxy Vulnerability Disclosed

First seen 18 Oct 2026, 02:38 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 18, 2026 at 02:39 UTC
  • •CVE-2026-76835 allows unauthenticated access via X-Forwarded-Uri manipulation.
  • •The vulnerability affects OAuth2 Proxy versions 7.15.2 to 7.15.4 with a CVSS score of 9.1.
  • •Operators must configure the --trusted-proxy-ip flag to mitigate the risk.

A vulnerability, CVE-2026-76835, has been identified in OAuth2 Proxy versions 7.15.2 to 7.15.4, allowing unauthenticated remote attackers to bypass authentication by manipulating the X-Forwarded-Uri header. The flaw, with a CVSS score of 9.1, arises when the --reverse-proxy is enabled and specific skip-auth rules are configured. This vulnerability is a continuation of CVE-2026-40575, which was patched in version 7.15.2, but the fix was ineffective due to default settings that trust all IP addresses. The patch for CVE-2026-76835 was released on October 1, 2026, in version 7.15.5, which tightened path matching and improved header resolution. As of now, there is no confirmed exploitation in the wild, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Operators are advised to configure the --trusted-proxy-ip flag and implement additional mitigation measures. The vulnerability primarily affects deployments using Kubernetes ingress architectures and multi-tenant SaaS backends.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-04-21
CVE-2026-40575 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-08-24
CVE-2026-76835 published
A critical authentication bypass vulnerability was disclosed, affecting OAuth2 Proxy versions 7.15.2 to 7.15.4.
github.com
2026-10-01
Patch released for CVE-2026-76835
OAuth2 Proxy version 7.15.5 was released, addressing the authentication bypass issue by tightening path matching and improving header resolution.
Forkast.News
2026-10-17
Reporting on vulnerability status
Forkast.News reported on the vulnerability's details, including its exploitation conditions and remediation steps for affected users.
Forkast.News

More articles in this cluster (2)

Following this threat?

Track CVE-2026-40575 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of OAuth2 Proxy are affected?
OAuth2 Proxy versions 7.15.2 through 7.15.4 are affected by CVE-2026-76835.
What should I do if I'm affected?
Upgrade to OAuth2 Proxy version 7.15.5 and configure the --trusted-proxy-ip flag to restrict trusted IPs.
Is there any confirmed exploitation of this vulnerability?
As of now, there are no confirmed instances of exploitation in the wild for CVE-2026-76835.