Security alert ยท 19 November 2026
A SonicWall VPN flaw lets attackers skip your MFA, and it is being exploited
SonicWall firewalls are everywhere in small and mid-size offices across Ontario and Canada. On 6 November 2026, SonicWall disclosed that a flaw in their SSL VPN lets someone with a valid password skip the SAML sign-in, and with it the multi-factor authentication you rely on. It is already being used by attackers, and there is no workaround. If your staff connect to the office through a SonicWall VPN, here is how to check in five minutes and what to do next.
Key takeaways
- Affected: Gen7 SonicOS 7.3.3-7015 and older, and Gen8 SonicOS 8.2.2-8015 and older, when SAML is used for SSL VPN logins.
- Fixed: SonicOS 7.3.4-7013 (Gen7) and 8.2.3-8015 (Gen8). Update now.
- What it does: a valid password alone can get through, skipping SAML and the MFA it enforces.
- After updating, check recent VPN logins, reset VPN passwords and confirm you have a backup an intruder could not have touched.
- Not using SAML on SSL VPN? SonicWall says you are not affected by this one, but the same update fixes six other flaws, so install it anyway.
What happened
SonicWall published advisory SNWLID-2026-0014 on 6 November 2026, covering seven vulnerabilities in SonicOS, the software that runs its firewalls. One of them, CVE-2026-19868, was already being exploited. The same day, the US Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities catalog, and the Canadian Centre for Cyber Security issued advisory AV26-1133 telling Canadian organizations to apply the updates.
SonicWall says its security team "investigated a report indicating potential exploitation". It has not said who was targeted or what the attackers did next. SonicWall rates the flaw 7.1 out of 10 (CVSS), which sounds moderate. Do not let the number slow you down: it is exploited, it sits on the device that guards your whole network, and there is no setting you can change to block it.
The flaw, in plain English
Many businesses connect their SonicWall SSL VPN to a sign-in service such as Microsoft Entra ID, Okta or Duo using SAML. That is how staff get the "approve this sign-in on your phone" step when they connect from home. It is a good setup, and it is exactly the one this flaw breaks.
- An attacker gets a valid username and password for one of your users, through phishing, a password reused from another breach, or guessing.
- Normally that is not enough: the VPN sends them to SAML, and SAML asks for the second factor.
- On an affected firewall, the attacker can authenticate another way and skip the SAML step entirely.
- No phone prompt, no MFA. They are on your network as that user.
SonicWall's own wording: the flaw "may allow a user with valid credentials" to bypass SAML, and "successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA)."
Are you affected? A five-minute check
You need to answer three questions. If any answer is "no", this particular flaw does not apply, but read the section on the other six flaws below.
| Question | Affected if |
|---|---|
| Which generation and SonicOS version is the firewall on? | Gen7 on 7.3.3-7015 or older (TZ, NSa, NSsp and NSv 270/470/870), or Gen8 on 8.2.2-8015 or older (TZ, NSa and NSv). Virtual NSv firewalls on VMware, Hyper-V, KVM, AWS and Azure count too. |
| Is SSL VPN turned on? | Yes, staff or contractors connect with SonicWall's SSL VPN client (NetExtender or Mobile Connect). |
| Do SSL VPN logins use SAML? | Yes, VPN users are sent to Microsoft Entra ID, Okta, Duo or another single sign-on page. |
The firmware version is shown on the firewall's management dashboard. If an outside IT provider manages your firewall, send them this page and ask for the version number and whether SAML is on for SSL VPN. You should have an answer the same day.
What to do
1. Update SonicOS now
Install 7.3.4-7013 or later on Gen7, or 8.2.3-8015 or later on Gen8. There is no workaround. Before you update, export a copy of the firewall's configuration and keep it somewhere off the firewall, so you can get back quickly if the update goes wrong. Plan for a short outage for anyone connected through the VPN.
Older Gen6 firewalls are not listed in this advisory. If you are still running one, check whether it still gets security updates at all; if not, it belongs on your replacement list.
2. Until you can update, shrink the exposure
- Limit SSL VPN access to the countries or IP addresses your staff actually connect from, if your setup allows it.
- Disable VPN accounts that are not in use: former staff, old contractors, test accounts.
- Make sure the firewall's management interface is not reachable from the internet. Two other flaws in this release (CVE-2026-107154 and CVE-2026-107155, both rated 8.8) are in that interface.
3. Check whether anyone already got in
The update closes the hole. It does not tell you whether someone used it before you closed it. SonicWall has not published signs to look for, so focus on what is unusual for your business:
- VPN logins at odd hours, from new countries, or from accounts that do not normally use the VPN.
- VPN sessions that do not have a matching sign-in in your SAML provider's logs (Entra ID, Okta or Duo). That mismatch is the clearest sign of this bypass.
- New admin accounts, new remote access tools, or security software switched off on servers.
Then reset passwords for VPN users, starting with administrators and finance, and make sure none of them reuse a password from another service.
4. Make sure your backups would survive an intruder
This is the step most businesses skip. A VPN is a front door, and ransomware groups who get through one usually go after the backups before they encrypt anything. We saw exactly that this month in the BlackNevas case, where attackers switched off and encrypted the backup system days before wiping the servers.
- Confirm that at least one backup copy is immutable or offline, so an account on your network cannot delete it.
- Check that your most recent backups completed and have not been changed or stopped in the last few weeks.
- Make sure the backup console has its own login and its own MFA, not the same account staff use for the VPN.
- If you have not restored from backup in the last 90 days, run a restore test.
The other six flaws in the same update
Even if you do not use SAML, install the update. None of these were reported as exploited on 6 November, but they are on the same device that guards your network:
| CVE | What it is | Severity |
|---|---|---|
| CVE-2026-107155 | Management interface cross-domain policy flaw; an unauthenticated attacker may perform unauthorized actions | 8.8 |
| CVE-2026-107154 | Management interface session validation flaw | 8.8 |
| CVE-2026-82308 | SSL VPN heap overflow before login; can crash the service | 7.5 |
| CVE-2026-77708 and CVE-2026-77709 | Buffer overflows in the TACACS+ login client, before login | 5.9 |
| CVE-2026-19703 | Weak password hashing on virtual (NSv) firewalls | 5.2 |
Why firewall flaws keep jumping the queue
Your firewall and VPN are the only things that sit directly on the internet and decide who gets in. That makes them the most valuable target an attacker has. The window between a fix and the first attacks has also shrunk: in October, a different SonicWall remote access flaw was fixed on 6 October and attack attempts reached honeypots two days later, as we noted in our November Patch Tuesday guide. Check Point also had an exploited flaw added to CISA's catalog on 13 November.
The practical answer for a small business is a simple routine: someone owns the firewall, checks for advisories weekly, updates within days for anything exploited, and knows the backups would still be there if the firewall ever lost.
Frequently asked questions
What is CVE-2026-19868?
It is a flaw in the SSL VPN service of SonicWall firewalls running SonicOS. Someone who already has a valid username and password can log in without going through the SAML sign-in, which also means skipping any multi-factor authentication that SAML enforces. SonicWall disclosed it on 6 November 2026.
Is my SonicWall firewall affected?
Only if all three are true: it is a Gen7 firewall on SonicOS 7.3.3-7015 or older, or a Gen8 firewall on SonicOS 8.2.2-8015 or older; SSL VPN is turned on; and SAML is used for SSL VPN logins. SonicWall says firewalls without SAML on SSL VPN are not affected by this flaw.
Which SonicOS version fixes it?
SonicOS 7.3.4-7013 or later for Gen7, and SonicOS 8.2.3-8015 or later for Gen8. SonicWall lists no workaround, so updating is the fix.
Is it being exploited?
Yes. SonicWall said it investigated a report of potential exploitation, and CISA added the flaw to its Known Exploited Vulnerabilities catalog on 6 November 2026, with a 20 November deadline for US federal agencies. Canada's Cyber Centre also issued advisory AV26-1133.
We have MFA. Why does this matter?
Because this flaw skips it. MFA is there to stop an attacker who has a stolen or guessed password. On an affected firewall, the password alone can be enough to get onto your network through the VPN.
We updated the firewall. Are we done?
Not quite. The update closes the hole but does not tell you whether someone already used it. Review recent VPN logins, reset passwords for VPN users, and make sure you have a recent backup that an attacker on your network could not have changed or deleted.
Not sure what your firewall is running, or whether your backups would survive?
We help small and mid-size businesses in Ontario, across Canada and in the United States close remote access gaps and make sure there is a clean way back if an attacker gets in.
- Backup and recovery check: we confirm at least one copy is immutable or offline and prove it restores.
- Remote access review: we check your firewall version, VPN settings, MFA and unused accounts.
- Endpoint security: we help you spot intruders on PCs and servers before they reach the backups.
Sources
- SonicWall PSIRT: SNWLID-2026-0014
- Canadian Centre for Cyber Security: SonicWall security advisory (AV26-1133)
- CISA: Known Exploited Vulnerabilities catalog
- IT Pro: SonicWall issues fixes for seven vulnerabilities, including an SSL-VPN flaw that bypasses MFA
- BleepingComputer: SonicWall warns of new SSL-VPN MFA bypass flaw exploited in attacks
- Tuskira: CVE-2026-19868 fix and exploit status
- Sherlock Forensics: Weekly security roundup, 1 to 14 November 2026
This article reflects public information as of 19 November 2026. Check SonicWall's advisory for the full list of affected models and the latest fixed versions.
