“We have MFA on the VPN. It was the first thing the insurance application asked about.” I hear some version of that in almost every renewal meeting, and it’s usually true.
Here is the catch: MFA protects you only on the login paths that actually require it. SonicWall has disclosed a flaw in its SSL VPN that can let a valid password reach the network without the SAML sign-in, and without the MFA that sign-in enforces. CISA says it is being exploited. The fix is a firmware update.
What SonicWall and CISA have confirmed
SonicWall’s security notice for SonicOS 7.3.4 and 8.2.3 (advisory SNWLID-2026-0014) covers several vulnerabilities in Gen7 and Gen8 firewalls, physical and virtual. The one that matters this week is CVE-2026-19868.
| Detail | What’s confirmed |
|---|---|
| What it does | According to CISA’s catalog entry, a user with valid credentials for an alternate authentication method may bypass SAML authentication controls, and may also bypass SAML-enforced MFA. |
| When it applies | Only when SAML is enabled for SSL VPN logins, per Help Net Security’s reporting on the advisory. |
| Affected | Gen7 on SonicOS 7.3.3-7015 and older. Gen8 on SonicOS 8.2.2-8015 and older. |
| Fixed | Gen7: 7.3.4-7013 and later. Gen8: 8.2.3-8015. |
| Exploitation | Added to CISA’s Known Exploited Vulnerabilities catalog on November 6, with a November 20 deadline for federal agencies. SonicWall said it investigated a report of potential exploitation. |
This is not a password-free attack. The attacker still needs a working username and password. But stolen and reused passwords are cheap, and the reason most businesses put MFA on the VPN is to make a stolen password useless on its own. This flaw takes that protection away on affected devices.
What isn’t known yet
SonicWall hasn’t published technical details, and no indicators of compromise had been released by SonicWall or CISA as of this writing. We don’t know who is exploiting it, how widely, or which organizations were affected. CISA lists ransomware use as “unknown.”
You may see posts tying this flaw to the ransomware crews that have gone after SonicWall VPNs in the past. That history is real, and it’s a good reason to move quickly. But no published source has linked this specific flaw to a ransomware campaign. You may also see it described as an unauthenticated bypass. It isn’t: SonicWall and CISA both describe an attacker who already has valid credentials.
Why this one matters for smaller businesses
SonicWall’s TZ and NSa firewalls are common in small and mid-size businesses: medical and dental practices, manufacturers, contractors, engineering and accounting firms. The VPN on that firewall is often how staff, owners and outside IT providers reach the network from home or a job site.
The setups most at risk are the ones that changed over time. A firm adds SAML and MFA through Microsoft or another identity provider, but the old local VPN accounts from before that project are still there. Everyone uses the new login, so nobody notices the old path is still open.
Gen6 SonicWall devices aren’t listed as affected, but they are past end of support and won’t get fixes for whatever comes next. If one is still running at your office, plan the replacement now.
What to do this week
- Ask your IT provider one question: is our firewall a SonicWall Gen7 or Gen8, is SAML turned on for the VPN, and what SonicOS version is it running?
- Patch. Gen7 to 7.3.4-7013 or later, Gen8 to 8.2.3-8015 or later. The same releases fix six other vulnerabilities.
- Close the side doors. Remove or disable local and directory VPN accounts that don’t need to exist. This narrows the exposure, but it isn’t a substitute for the patch.
- If you can’t patch right away, consider limiting VPN access to known locations or turning the VPN off until you can. SonicWall hasn’t published a workaround.
- Check the logs. Look for VPN logins that succeeded with no matching sign-in and MFA approval in your identity provider. Reset passwords for any account that logged in that way, and review what it accessed.
- Write it down: the date you patched, the version, and who did it.
Where cyber insurance fits
If someone used this flaw to get into your network, a cyber policy is designed to respond to what follows: forensic investigation, breach counsel, ransomware response, restoration, business interruption, notification if sensitive information was exposed, and defense of claims, subject to its terms. Call your agent or your carrier’s breach hotline early. Many policies require you to use their approved vendors.
Two things deserve a look now. First, nearly every cyber application asks whether MFA is required for all remote access. If there’s a login path on your VPN that doesn’t go through MFA, by design or because of this flaw, your answer may not match reality. Update your IT provider’s notes, fix the gap, and talk to your agent if your last application needs a closer look. Second, some policies reduce or exclude coverage when a loss starts with a known exploited vulnerability that went unpatched past a set period. This one is on CISA’s list. Patch it and keep the record.
MFA is a lock on one door. Make sure it’s the only door.
Sources
- SonicWall: SonicOS 7.3.4 and 8.2.3 Security Advisory – Gen 7 and Gen 8 Firewalls
- SonicWall PSIRT: SNWLID-2026-0014
- CISA: Known Exploited Vulnerabilities Catalog (CVE-2026-19868)
- NIST National Vulnerability Database: CVE-2026-19868
- Help Net Security: Exploited SonicWall SSL-VPN flaw lets attackers bypass SAML-enforced MFA
- Cyber Security News: CISA warns of SonicWall SonicOS SSLVPN vulnerability exploited in attacks