CVE-2026-76835
Auth bypass in oauth2-proxy via spoofed X-Forwarded-Uri allowing access to protected paths
Is CVE-2026-76835 being exploited?
Not confirmed. CVE-2026-76835 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-76835?
CVE-2026-76835 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76835?
Yes. A fix has been recorded for CVE-2026-76835. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76835 affect?
CVE-2026-76835 affects oauth2-proxy (reverse-proxy mode, default trusted_proxy_ip unset). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76835?
Restrict trusted_proxy_ip, disable trusting forwarded headers, and apply vendor patch when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can bypass OAuth2 Proxy auth by spoofing X-Forwarded-Uri to match allow-listed routes, accessing protected upstream endpoints.
Immediate action required
- affected>= 7.15.2 and <= 7.15.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.