CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog on November 6, with a November 20 deadline for US federal agencies. It affects the SSLVPN service in SonicWall's SonicOS, and the vendor's own classification is the interesting part: CWE-308, use of single-factor authentication. In SonicWall's words, the flaw "may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls," and successful exploitation "may also bypass SAML-enforced multi-factor authentication."
Read that twice. The multi-factor authentication was enforced. Someone with credentials for a different login path went around it.
Who is affected
Affected builds are Gen7 7.3.3-7015 and earlier and Gen8 8.2.2-8015 and earlier, fixed in 7.3.4-7013 and 8.2.3-8015 respectively. SonicWall says there are no workarounds. It only applies where SAML is enabled for SSLVPN logins, so if you authenticate VPN users another way this specific flaw is not yours.
Unlike most appliance stories we cover, this one lands squarely on small businesses. SonicWall is not enterprise-only kit. It is the firewall in a great many Canadian offices of ten to fifty people, usually installed by an IT provider and rarely thought about again.
Two things being reported loosely
A CVSS score of 8.8 is circulating for this. That figure belongs to the bulletin as a whole, which covers seven SonicOS flaws; this specific CVE sits around 7.1, and it is the only one of the seven on CISA's exploited list. Worth getting right if you are explaining urgency to someone.
And on exploitation, the public detail is thin. SonicWall says its team "has investigated a report indicating potential exploitation of this vulnerability." Neither the vendor nor CISA has described the attacks, who is behind them, or how many organizations were hit. KEV listing means CISA is satisfied exploitation is real, not that a campaign has been documented.
The part worth keeping after this patch
Strip away SonicWall and you have a pattern that exists in most small businesses: multi-factor authentication enforced on one route into a system, while a second route still accepts a password alone.
Think about where that shape appears. Microsoft 365 with modern authentication locked down but a legacy protocol still enabled. A VPN with MFA for staff and a service account exempted so an integration keeps working. An admin console protected properly and an API key that bypasses the console entirely. A cloud app behind single sign-on that also kept its original local login. In each case the control is genuinely enforced, and genuinely irrelevant, because the attacker uses the other door.
That is why "do you have MFA" is the wrong question and "is there any way into this system that does not require MFA" is the right one. It is the same thinking behind auditing what else can reach your tenant, where applications authenticate with their own credentials and never see an MFA prompt at all.
What to actually do
- If you run SonicWall, find your version this week. Gen7 below 7.3.4-7013 or Gen8 below 8.2.3-8015 needs the update, and there is no workaround to lean on.
- Ask your IT provider directly: do we have SonicWall SSLVPN with SAML enabled, are we on a fixed build, and have you reviewed VPN logins for anything unusual. One email.
- Then ask the general question of every important system: list the ways in, and check each one for MFA. Not the main login, every login.
- Hunt for the exemptions you created on purpose. Service accounts, break-glass admin accounts, the integration someone excluded in 2024 so it would stop failing. Each is a documented bypass sitting in your own configuration.
- Review VPN access logs for logins that succeeded without a second factor, which is the signal this class of flaw produces.
- Prefer fewer authentication paths. Every alternate method you keep enabled is another thing that has to be configured correctly forever.
The takeaway
Multi-factor authentication is still the highest-value control a small business can turn on, and nothing here changes that. What this flaw illustrates is that enforcement is only as good as the number of doors it covers. The useful hour this week is not patching one firewall, it is listing every way into your two or three most important systems and confirming that each one actually asks for a second factor.