SonicWall SSL VPN Flaw Lets Attackers Bypass SAML Sign-In and MFA (CVE-2026-19868)
SonicWall firewalls running SonicOS 7.3.3-7015 or 8.2.2-8015 and earlier can let someone with a valid LDAP, RADIUS or TACACS+ login get around SAML sign-in, including SAML-enforced MFA, on the SSL VPN. It is being exploited. Upgrade to 7.3.4-7013 or 8.2.3-8015, or later.
What happened
On 6 November 2026, SonicWall published a security advisory covering seven flaws in SonicOS, the software that runs its firewalls. One of them, CVE-2026-19868, affects the SSL VPN that staff use to connect to the office network from home or on the road. The same day, CISA added it to its catalog of vulnerabilities known to be exploited in real attacks.
The flaw sits in how the firewall enforces sign-in. If your SSL VPN uses SAML (single sign-on through a provider such as Microsoft Entra ID, Okta or Google), someone who has valid credentials for one of the firewall's other sign-in methods (LDAP, RADIUS or TACACS+) can get around the SAML step. SonicWall says this can also bypass multi-factor authentication when MFA is enforced through SAML.
In practice, that means a stolen or guessed directory password could be enough to get onto your network, even if you thought MFA was protecting the VPN.
Who is affected
You are affected if all of these are true:
- You use a SonicWall Gen7 or Gen8 firewall, either hardware (TZ, NSa or NSsp series) or virtual (NSv).
- It runs SonicOS 7.3.3-7015 or earlier (Gen7) or 8.2.2-8015 or earlier (Gen8).
- SAML is turned on for SSL VPN logins.
SonicWall notes the flaw only affects the SSL VPN when SAML is enabled for it. If you don't use SAML for the VPN, this particular flaw does not apply, but the same advisory fixes six other issues, including denial-of-service bugs in the SSL VPN and the management interface, so the update is still worth applying.
Is it being exploited?
Yes. SonicWall says it has investigated a report of potential exploitation and urges customers to upgrade as soon as possible. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 6 November 2026 and gave US federal agencies until 20 November to fix it. CISA has not said whether ransomware groups are using it.
When to get outside help
Many small businesses had their SonicWall installed by an IT provider and haven't logged in to it since. If you're not sure which firmware you run, whether SAML is on, or who has admin access, a managed security provider can check and update the firewall, usually in a single session. If you see VPN logins you can't explain since early November, treat it as a possible break-in and bring in incident response help before you change anything.
What to do
- Find your firmware version. Sign in to the firewall's management interface and check the SonicOS version on the dashboard.
- Upgrade. SonicWall's fixed versions are 7.3.4-7013 or later for Gen7 firewalls and 8.2.3-8015 or later for Gen8 firewalls. Download them from MySonicWall.
- If you can't upgrade straight away and you use SAML for the SSL VPN, SonicWall's workaround is to disable or delete every active LDAP, RADIUS and TACACS+ authentication server on the firewall. You'll find them under Device > Users > Settings > Authentication, in the Configure RADIUS, Configure LDAP and Configure TACACS+ sections. Check this won't lock out users who depend on those methods first.
- Review recent VPN logins for unfamiliar users, times or locations since the start of November.
Related guides
Sources
- SonicWall SonicOS Affected by Multiple Vulnerabilities (SNWLID-2026-0014) (SonicWall PSIRT)
- Known Exploited Vulnerabilities Catalog: CVE-2026-19868 (CISA)
- CVE-2026-19868 (CVE Program)
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
