CVE-2026-40575 is an authentication bypass vulnerability in OAuth2 Proxy affecting versions 7.5.0 through 7.15.1. In deployments where --reverse-proxy is enabled and at least one --skip-auth-regex or --skip-auth-route rule is configured, OAuth2 Proxy may trust a client-supplied X-Forwarded-Uri header. An attacker can spoof this header so that OAuth2 Proxy evaluates authentication and skip-auth decisions against a different URI path than the one actually forwarded to the upstream application. As a result, requests for protected resources can be misclassified as exempt from authentication, allowing access without a valid authenticated session.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
X-Forwarded-Uri header at the reverse proxy or load balancer, or 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 is reachable only through a trusted reverse proxy. Remove, narrow, or otherwise minimize --skip-auth-regex and --skip-auth-route rules where feasible. For nginx-based deployments, ensure nginx sets X-Forwarded-Uri itself and does not pass through a client-supplied value.Patch, then assume compromise.
--reverse-proxy together with --skip-auth-regex or --skip-auth-route and validate that forwarded URI headers are derived only from trusted infrastructure rather than client input.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.