Eight authentication bypasses in three weeks. Between September 26 and October 17, 2026, the enterprise landscape suffered a cascade of failures that, while reported as isolated incidents, reveal a singular, systemic rot: federation and proxy layers operating on a ‘trust-by-default’ basis, blindly accepting client-supplied assertions without binding them to the local security context.
The Keycloak masked-secret reuse (CVE-2026-15943) demonstrated how delegated admin actions can expose stored IdP client secrets when token URLs are modified. Shortly after, Better Auth OAuth state reuse (CVE-2026-110862, CVSS 9.3) highlighted a framework-level failure where IdP-provided email verification status was accepted without local cross-checking. The Frontegg SAML validation failure (CVE-2026-75800, CVSS 9.8) underscored the danger of missing signature and issuer validation, leading to unauthenticated admin takeover. In the infrastructure space, Citrix SAML patch issues (CVE-2026-107406, CVSS 9.5) saw emergency fixes failing to address the underlying vulnerability, while AD FS spoofing CVEs (CVE-2026-108131/CVE-2026-96222) emerged precisely as new key enforcement mechanisms were activated.
Budibase OIDC invite hijacking (CVE-2026-100684, CVSS 9.2) extended this trend, where the authentication flow defaulted to pending invites based solely on email addresses. The OAuth2 Proxy header bypass (CVE-2026-76835, CVSS 9.1) revealed that default configurations for trusted proxy IPs can effectively nullify existing security guards. These eight incidents in three weeks are not a coincidence; they are the spine of a systemic shift in how identity assertions are processed.
These failures stem from the decoupling of the assertion from the local environment. Systems are increasingly designed to ingest tokens or headers from external IdPs or proxies and treat them as absolute truth. When these systems fail to perform secondary validation—such as checking if the assertion was intended for the specific local resource or if the user state matches local records—they become vulnerable to manipulation. The assertion is treated as a pass-through, rather than a verifiable claim.
The scale of this problem is expanding rapidly. According to the Cloud Security Alliance (CSA), 78% of OAuth and SAML implementations currently lack proper assertion binding validation. This is occurring against a backdrop of surging vulnerability disclosures. Google Threat Intelligence (GTI) data indicates that monthly CVE disclosures have doubled from 5,045 to 10,740. Furthermore, the rise of agent middleware has introduced a new vector, with a 347% surge in related flaws, while 82% of Model Context Protocol (MCP) servers exhibit file-operation vulnerabilities. This aligns with our earlier trend analysis, which notes a 2.75x year-over-year increase in identity-based attacks.
The attack surface is not contracting; it is becoming more complex. As organizations integrate more agentic workflows and middleware, the reliance on federated identity increases. If the underlying federation layers continue to trust assertions without local binding, the frequency of these bypasses will likely accelerate. The shift toward automated, machine-to-machine authentication creates more opportunities for these structural flaws to be exploited at scale.
Operators must immediately move away from implicit trust. First, audit all federation and proxy configurations to ensure that assertion binding is strictly enforced; do not rely on the IdP to provide the final word on user identity or authorization. Second, implement local validation checks that cross-reference incoming assertions against local state, such as pending invite codes or specific session requirements. Third, review default settings in proxy layers, particularly those handling headers like X-Forwarded-Uri, to ensure they are not overly permissive. Finally, treat identity middleware as a high-risk component, applying the same rigorous validation standards to these services as you would to your primary authentication gateway.
