Bastion Cyber Threat Brief | November 8, 2026: SonicWall SSL-VPN Flaw Can Bypass SAML MFA

Executive takeaway
If your organization uses SonicOS SSL-VPN with SAML, prioritize an exposure check and the appropriate vendor update. Do not assume an MFA policy alone closes this flaw. Source
What changed
SonicWall published advisory SNWLID-2026-0014 on November 6, 2026. For CVE-2026-19868, it says it investigated a report indicating potential exploitation. Canada’s Cyber Centre separately records a November 6 addition to CISA’s Known Exploited Vulnerabilities catalog. Source · PSIRT advisory
Who is affected
SonicWall says this flaw applies to its SSL-VPN interface or service only when SAML is enabled for VPN logins. A user needs valid credentials for an alternate authentication method; exploitation may bypass SAML controls and SAML-enforced MFA. This is not a claim of credential-free access. Source
What to do
Check your firewall generation, installed firmware and SSL-VPN SAML configuration. SonicWall lists fixes for Gen7 and Gen8 physical and virtual firewalls; use its current platform-specific table to select the update. The PSIRT advisory lists no workaround. Source · PSIRT advisory
Bastion analysis
For growing businesses and enterprises, including teams in the 757, make the check specific: which firewall, which authentication configuration, and who verifies the installed firmware after maintenance? If a provider manages remote access, ask for those details rather than accepting “MFA is enabled” as the answer.
Limits and verification
This brief does not establish compromise of your environment or the scale of exploitation. SonicWall’s first-publication and last-update dates are November 6; no time is supplied. Verified as of November 8, 2026, 8:55 a.m. EST. Source

Comments