What changed
A different login method could bypass SAML
A VPN may appear to sit behind a central identity provider and its MFA policy. SonicWall's CVE-2026-19868 shows why teams need to check the path a sign-in actually takes. According to SonicWall, a user with valid credentials for an alternate authentication method may bypass SAML authentication controls in the SonicOS SSL-VPN service. That can also bypass MFA enforced through the SAML flow.
This is not a claim that every MFA technology can be defeated, or that an attacker can log in without any credentials. The published condition specifically requires valid alternate-method credentials. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 6 November, increasing the priority for exposed firewalls.
Keep the scope precise
Defender workflow
Follow the session from firewall to identity provider
- 1
Identify affected deployments. Inventory internet-facing SonicOS SSL-VPN appliances and compare their running firmware with SonicWall's advisory.
- 2
Check authentication methods. Confirm whether alternate login methods remain enabled, which accounts can use them, and whether those routes match the organization's remote-access policy.
- 3
Patch and investigate. Apply the vendor fix. Review VPN sessions for successful logins that lack the expected identity-provider authentication and MFA events.
Defender note
Do not stop at the policy diagram
The meaningful test is whether a real VPN session traversed the control everyone assumed was mandatory. Correlate firewall and identity-provider logs before dismissing a login as protected by MFA.