SonicWall SSL VPN flaw lets attackers skip MFA: what to do

By Sridhar Thewar, Founder & CEO · 4 min read · Published
Short version: If your SonicWall firewall uses SAML, for example Microsoft Entra ID or Okta, for SSL VPN logins, a flaw tracked as CVE-2026-19868 can let someone with a valid password for another login method get in without passing SAML, and so without its MFA check. CISA says it is being exploited. Upgrade Gen7 firewalls to SonicOS 7.3.4-7013 and Gen8 to 8.2.3-8015, then check who logged in.

SSL VPN is the front door to most office networks, and MFA is the lock that makes a leaked password useless. This flaw quietly removes that lock. This post reflects what was published up to 12 November 2026.

What happened

SonicWall has released SonicOS updates that fix seven flaws in its Gen7 and Gen8 firewalls, physical and virtual. One of them, CVE-2026-19868, is in the SSL VPN service, and SonicWall said it had investigated a report of potential exploitation. On 6 November 2026, CISA added the flaw to its Known Exploited Vulnerabilities catalogue, which it does on evidence of active exploitation, and gave US federal agencies until 20 November to fix it.

No one has published details of the attacks. It is not known how many organisations were affected or what the attackers did once they were in.

Who is affected

This is not a way in without a password. The attacker needs valid credentials for another way of logging in to the SSL VPN. What the flaw removes is the protection added on top: the SAML sign-in and any MFA enforced through it. In plain terms, a stolen or guessed password can be enough again.

Gen6 firewalls are not listed as affected, but they are past end of support, and SonicWall advises moving to Gen8.

Why this one matters

Passwords leak all the time, through phishing, reuse and malware on home laptops. MFA is what makes a leaked VPN password useless, and this flaw takes it away. SonicWall SSL VPN has been here before. Help Net Security notes that an earlier SonicWall MFA bypass, CVE-2024-12802, was exploited, and that Akira ransomware affiliates broke into SonicWall SSL VPN accounts in 2025 even where one-time-password MFA was switched on. Our post on how the firewall became the way in covers the wider pattern.

What to do

This week

  1. Find out where you stand: whether SSL VPN uses SAML, and which SonicOS version every firewall runs, including standby units in high-availability pairs and branch firewalls.
  2. Upgrade: Gen7 to 7.3.4-7013 or later, Gen8 to 8.2.3-8015 or later. SonicWall lists no workaround, so the upgrade is the fix. The same release fixes six more SonicOS flaws, including two serious ones in the management interface, so upgrade even if you do not use SAML.
  3. If you cannot upgrade straight away, reduce exposure: limit which addresses can reach SSL VPN where your users connect from known places, and keep the management interface off the internet. Neither fixes the flaw. If the risk is too high to wait, switching SSL VPN off until you can upgrade is the only way to remove it.

After upgrading

  1. Compare VPN logins with your identity provider. Look for SSL VPN logins that succeeded without a matching sign-in and MFA check in Entra ID, Okta or whichever provider you use.
  2. Reset the password of any account that logged in that way, and check what those sessions reached.
  3. Remove logins you do not need. SonicWall has not said which other login method the attack uses, so the fewer ways there are to sign in to SSL VPN, such as local firewall accounts or old LDAP and RADIUS logins, the smaller the gap.
  4. Keep enough logs. If your firewall only keeps a few days of logs, step 1 has nothing to check. CERT-In expects 180 days; see CERT-In's 180-day log rule.

If you are still on Gen6

It no longer gets fixes, so plan the replacement now rather than after the next flaw. Our firewall replacement checklist covers how to do it without a bad Monday, and it is a good moment to ask whether VPN or ZTNA suits your remote access better.

Sources

Frequently asked questions

Is SonicWall CVE-2026-19868 being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalogue on 6 November 2026 on evidence of active exploitation, and SonicWall said it had investigated a report of potential exploitation.

Which SonicOS versions fix it?

SonicOS 7.3.4-7013 or later for Gen7 firewalls, and 8.2.3-8015 or later for Gen8.

We do not use SAML for SSL VPN. Are we affected?

Not by this flaw, which only matters when SAML is enabled for SSL VPN logins. Upgrade anyway, because the same release fixes six other SonicOS flaws.

Is there a workaround?

SonicWall lists none, so upgrading is the fix. Limiting who can reach SSL VPN reduces exposure but does not remove the flaw.

Running SonicWall SSL VPN?

We upgrade firewalls, tighten who can reach SSL VPN, and set up logging that can answer who logged in and when.

Book a free consultation