cve.bz

CVE-2026-76835 oauth2-proxy oauth2-proxy: Authentication Bypass by Spoofing

9.3 criticalEPSS 0.5%Fix available

Critical (9.3) in oauth2-proxy oauth2-proxy. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/oauth2-proxy/oauth2-proxy/v7 7.15.2.

On this page
OAuth2 Proxy honours a client-supplied X-Forwarded-Uri header when deciding whether a request may skip authentication, because the guard added for CVE-2026-40575 is inert in the default reverse-proxy configuration. GetRequestURI in pkg/requests/util/util.go prefers that header over the real request URI whenever CanTrustForwardedHeaders returns true, and isAllowedPath in oauthproxy.go matches the skip_auth_routes and skip_auth_regex allow list against the resulting path. CanTrustForwardedHeaders in pkg/apis/middleware/scope.go grants that trust when the caller's address is in the trusted proxy set, and buildTrustedProxyNetSet falls back to defaultTrustedProxyIPs, which is 0.0.0.0/0 and ::/0, whenever reverse proxy mode is enabled without trusted_proxy_ip configured. Every client is therefore treated as a trusted proxy. An unauthenticated attacker can request a protected upstream path while setting X-Forwarded-Uri to a value matching an allow-listed route, so the skip-auth decision is made against the spoofed value while the upstream receives the protected path unchanged.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-290 Authentication Bypass by Spoofing
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-76835 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76835?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76835?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-76835 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
oauth2-proxyfrom 7.15.2 through 7.15.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7x63-xv5r-3p2xGogithub.com/oauth2-proxy/oauth2-proxy/v7>=7.5.0 <7.15.27.15.2
GO-2026-5236Gogithub.com/oauth2-proxy/oauth2-proxyall versionsno fix published
GO-2026-5236Gogithub.com/oauth2-proxy/oauth2-proxy/v7>=7.5.0 <7.15.27.15.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hathummingbird:1oauth2-proxy0:7.15.5-0.1.hum1RHSA-2026:74536

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity as an unauthenticated remote attacker can bypass authentication checks to access protected upstream services without authorization. The issue occurs when OAuth2 Proxy operates in reverse proxy mode with route-skipping rules enabled and lacks an explicitly restricted trusted proxy configuration, causing it to trust header inputs from any remote source. Because authentication enforcement fails before requests are dispatched upstream, unauthorized users can gain full access to sensitive internal endpoints.

This is vulnerability is rated as Important rather than Critical because the reverse proxy mode is required which is not part of the default configuration for Red Hat products.

Red Hat's mitigation

To mitigate this issue without patching, apply one of the following configuration controls:

1. Restrict trusted proxy IP addresses in OAuth2 Proxy:

Explicitly set the `--trusted-proxy-ip` command-line argument (or the `trusted_proxy_ip` configuration file parameter) to the specific IP address or CIDR range of authorized upstream reverse proxies or load balancers rather than relying on the default:

```

--trusted-proxy-ip=<TRUSTED_PROXY_IP_OR_CIDR>

```

2. Sanitize forwarded headers at the perimeter reverse proxy:

Configure intermediate ingress controllers or front-facing reverse proxies (such as NGINX) to strip client-supplied `X-Forwarded-Uri` headers or overwrite them with the actual request URI before forwarding traffic to OAuth2 Proxy:

```

proxy_set_header X-Forwarded-Uri $request_uri;

```

Warning: Applying these configuration adjustments requires restarting or reloading the affected OAuth2 Proxy or front-end proxy services, which may cause a brief interruption to active network sessions.

ProductPackageStateAdvisory
Red Hat Hardened Imagesoauth2-proxy-main-7.15.5-0.1.hum1Fixed 2026-10-01RHSA-2026:74536
Red Hat Ceph Storage 8rhceph/oauth2-proxy-rhel9Not affected
Red Hat Ceph Storage 9rhceph/oauth2-proxy-rhel10Not affected
Red Hat Ceph Storage 9rhceph/oauth2-proxy-rhel9Not affected
Red Hat OpenShift Dev Spacesdevspaces/oauth2-proxy-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-76835.

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-473 Signature Spoof
  • CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
  • CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON