SonicWall has released SonicOS updates that fix seven vulnerabilities, including CVE-2026-19868, an SSL VPN flaw that lets an attacker with valid credentials for an alternate authentication method bypass SAML authentication controls, potentially including multi-factor authentication (MFA) enforced through SAML. SonicWall published advisory SNWLID-2026-0014 on November 6, 2026, and said its product security team "has investigated a report indicating potential exploitation of this vulnerability," according to BleepingComputer.
The same day, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog, a list reserved for flaws with evidence of active exploitation. The Canadian Centre for Cyber Security recorded the listing in its own notice, AV26-1133. Federal civilian executive branch agencies have until November 20 to secure affected systems.
What the flaw does
SonicOS runs SonicWall's firewalls, and its SSL VPN service provides remote access to the networks behind them. CVE-2026-19868 affects only SSL VPN services configured to use SAML authentication, BleepingComputer reported, and carries a CVSS score of 7.1. The attacker needs working credentials for another authentication method that the appliance accepts. With those, the SAML controls, and any MFA that SAML enforces, can be bypassed.
That precondition offers less comfort than it might seem. Organizations put MFA in front of a VPN because passwords leak and get reused. A flaw that sidesteps the second factor leaves the login resting on the password alone.
BleepingComputer reported that Ryan Harris of The Electronic Office discovered and reported the vulnerability.
Affected versions and the other six flaws
BleepingComputer, reporting on the advisory, lists SonicOS Gen7 7.3.3-7015 and earlier and Gen8 8.2.2-8015 and earlier as affected, with fixes in 7.3.4-7013 and 8.2.3-8015, and says SonicWall reports no workarounds. The Canadian notice describes affected versions as those prior to 7.3.4-7013 and prior to 8.2.2-8015, which does not match on Gen8. Administrators should check the fixed build for their model against SonicWall's advisory and confirm the running version after upgrading.
The other six vulnerabilities are not limited to SAML deployments. According to BleepingComputer, they include two management interface flaws rated 8.8 that let unauthenticated attackers perform unauthorized operations under specific conditions. The rest are pre-authentication buffer overflows in the SSL VPN and TACACS+ services that can cause denial of service, and a weak password hashing issue in virtual appliances. A firewall that does not use SAML for VPN logins is outside CVE-2026-19868 but may still need the update.
What is known about the attacks
Very little. SonicWall has not shared details of the reported exploitation, BleepingComputer noted, and the public notices name no attacker and give no count of affected appliances.
Until more detail emerges, the firewall's own authentication logs are the most direct evidence available. On an appliance set to require SAML for SSL VPN access, a successful VPN session authenticated through a different method warrants investigation.
An earlier MFA bypass on SonicWall VPNs
This is not the first exploited MFA bypass on SonicWall SSL VPNs this year. In May, ReliaQuest reported what it assessed with medium confidence to be the first in-the-wild exploitation of CVE-2024-12802, an authentication bypass disclosed in early 2025, in activity between February and March 2026. In that flaw, MFA protection applied to the UPN and SAM login formats separately rather than to the user behind them, so a login through the unprotected format skipped the second factor.
On Gen6 appliances, the firmware update alone did not close that gap. SonicWall's advisory required six further manual reconfiguration steps, and ReliaQuest found devices that had been patched but not reconfigured being exploited, as BleepingComputer reported on May 20. On Gen7 and Gen8 devices, the firmware update was enough.
The two flaws are different bugs, and nothing public connects the attacks. What they share is a second route into the VPN that does not carry the MFA requirement with it. Teams reviewing remote access after this patch have reason to check every authentication method their appliances accept, not only the one users are meant to use.
What happens next
The November 20 deadline binds only US federal civilian agencies. For other organizations, the KEV listing is the clearest public signal that the flaw is being used against real targets. A revised advisory with indicators of compromise, or findings from an incident response firm, would give defenders the first public account of how the attacks work and how far they have spread.
Sources
- SonicWall PSIRT: "SonicWall SonicOS Affected By Multiple Vulnerabilities" (SNWLID-2026-0014). 6 November 2026. https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014
- CISA: Known Exploited Vulnerabilities Catalog, CVE-2026-19868. 6 November 2026. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868
- Canadian Centre for Cyber Security: "SonicWall security advisory (AV26-1133)." 6 November 2026. https://www.cyber.gc.ca/en/alerts-advisories/sonicwall-security-advisory-av26-1133
- BleepingComputer: "SonicWall warns of new SSL-VPN MFA bypass flaw exploited in attacks." 6 November 2026. https://www.bleepingcomputer.com/news/security/sonicwall-warns-of-new-ssl-vpn-mfa-bypass-flaw-exploited-in-attacks/
- ReliaQuest: "VPN Exploitation When Patched Doesn't Mean Protected." 19 May 2026. https://reliaquest.com/blog/threat-spotlight-vpn-exploitation-when-patched-doesnt-mean-protected/
- BleepingComputer: "Hackers bypass SonicWall VPN MFA due to incomplete patching." 20 May 2026. https://www.bleepingcomputer.com/news/security/hackers-bypass-sonicwall-vpn-mfa-due-to-incomplete-patching/
