Loading vulnerability…
CVE-2026-34457 is a configuration-dependent authentication bypass vulnerability in OAuth2 Proxy affecting versions prior to 7.15.2. The issue occurs in deployments that use OAuth2 Proxy with an auth_request-style integration, such as nginx auth_request, and also enable either the --ping-user-agent option or --gcp-healthchecks. In affected configurations, OAuth2 Proxy incorrectly treats any request carrying the configured health check User-Agent value as a successful health check regardless of the requested path. As a result, requests that should be subject to authentication checks can be incorrectly marked as authorized, enabling bypass of the proxy’s authentication enforcement for protected upstream resources.
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.
Patch, then assume compromise.
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.
4 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.