SonicWall VPN flaw CVE-2026-19868 lets a valid password skip SAML MFA; here's how to check and patch your clients' SonicWall firewalls.
A stolen VPN password is supposed to be only half a break-in, because the second factor still blocks the door; on some SonicWall firewalls, it could be enough. On 6 November 2026, CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog, a SonicOS SSL VPN flaw that lets valid credentials from another login method skip SAML-enforced MFA. Check every client's SonicWall VPN login settings and firmware build today.
CVE-2026-19868 is a SonicOS SSL VPN authentication flaw: the CVE record says a user with valid credentials for an alternate authentication method may bypass SAML authentication controls, including SAML-enforced MFA. SAML is the single sign-on standard that hands staff logins to an identity provider; MFA is the extra code or phone prompt after the password.
Yes, it is being exploited. CISA added it on 6 November 2026 and set a due date of 20 November 2026 for federal agencies. According to BleepingComputer, SonicWall said it "investigated a report indicating potential exploitation" but has not shared attack details. NVD lists 7.5 (CVSS); BleepingComputer reports 7.1. The same report notes October exploitation attempts against CVE-2026-102255 in SonicWall's SMA1000 remote-access appliances, and credits Ryan Harris of The Electronic Office with finding this one.
The SonicWall SSL VPN MFA bypass hits SonicOS SSL VPN only when SAML is enabled for SSL VPN logins, a limit SecurityOnline quotes from SonicWall. The fixed builds below come from BleepingComputer and SecurityOnline, because SonicWall's advisory SNWLID-2026-0014 page did not render for us.
Patch even without SAML. The same update fixes CVE-2026-107154 and CVE-2026-107155, each CVSS 8.8, management-interface flaws that could let an unauthenticated attacker perform unauthorized operations under specific conditions, plus pre-login crash bugs in the SSL VPN and TACACS+ services, per SecurityOnline.
These steps run in the SonicOS web console and on your workstation, with no shell on the firewall; menus follow SonicOS 7.3 docs. No source dates the first exploitation, so search the oldest retained logs in the client's SIEM or syslog archive: on-device logs are short, and a clean result there doesn't rule out an earlier break-in. SonicWall has published no indicators, so no hash search is possible.
Preserve evidence. Export the configuration from Device | Settings > Firmware and Settings, the Tech Support Report and the System Logs as CSV, then copy and hash them. Pass: the .sha256 file lists every exported file.
# Your workstation (Linux, or macOS with coreutils for sha256sum)
D=~/ir/client-sonicwall-$(date +%F); mkdir -p "$D"
cp -a ~/Downloads/<config.exp> ~/Downloads/<tsr-file> ~/Downloads/<logs.csv> "$D"/
sudo find "$D" -type f -exec sha256sum {} + | sudo tee "$D.sha256"
Confirm the build and login type. Read the firmware under Home > Dashboard | System > General and the authentication type under Network > SSL VPN > Server Settings. Pass: the build is 7.3.4-7013, 8.2.3-8015 or later, or the type isn't SAML.
Sweep client IPs. This checks only the SSL VPN's default port 4433 and port 443, so the asset inventory stays the primary list. Pass: every IP that answers is a firewall you read in check 2.
# clients.txt: one public firewall IP per line; 000 = no answer
while read -r H; do for U in "https://$H:4433/" "http://$H:4433/" "https://$H/" "http://$H/"; do
printf '%s %s\n' "$U" "$(curl -sk -m 5 -o /dev/null -w '%{http_code}' "$U")"
done; done < clients.txt
Match VPN logins to identity-provider sign-ins. A VPN login with no matching sign-in, or from an unexpected Client WAN IP on Network > SSL VPN > Status, is the skipped-MFA session SecurityOnline says to review. Pass: every login has a matching sign-in.
# Same shell as check 1. Message wording varies by build; if empty,
# filter System Logs to SSL VPN events before exporting.
grep -iE 'ssl ?vpn' "$D"/*.csv | grep -i login
Look for new users and config changes. Read MONITOR | Logs > Auditing Logs, SSLVPN Services members and Device > Users > Local Users & Groups. Pass: the client recognises every entry and member.
For any unmatched login, treat it as a likely compromise and escalate: open a SonicWall support case quoting CVE-2026-19868 with the Tech Support Report.
Close the door: upgrade. Use Upload Firmware and boot "Uploaded Firmware with current configuration"; expect a 5–8 minute outage. If that can't happen today, switch SSL VPN off for the WAN zone under SSL VPN Status on Zones, which cuts remote access. Pass: check 2 shows a fixed build.
Remove footholds. Delete unknown local users with the Configure column's Delete icon and remove unknown SSLVPN Services members. Pass: rerun check 5 and only expected names remain.
Rotate credentials. Reset local user and admin passwords, have the client reset directory passwords for accounts flagged in check 4, and change the bind password under Configure LDAP. Pass: a VPN login with an old password fails.
Take management off the internet. Under Network | System | Interfaces, edit the WAN interface and clear HTTPS and SSH management; admins then need a LAN path. Pass: the command below prints 000.
# From outside the client network; 000 = no answer
curl -sk -m 5 -o /dev/null -w '%{http_code}\n' https://<wan-ip>/
Rerun checks 2 to 5. Pass: each check meets its own Pass line.
KinoSec's autonomous external network pentest checks whether each client's SonicWall SSL VPN portal and management page answer from the internet, and lists them in a report with remediation you can hand the client. That is the map checks 2 and 3 need: which firewalls face the internet, and whether the management interface fixed by the same update is exposed. It tests what an attacker could reach from the outside; it doesn't read the identity provider's sign-in log, which check 4 does. For an MSP with many client firewalls, running it on demand turns "did we patch everything?" into a list you can tick off.
No. SonicWall says the flaw "ONLY impacts the SonicOS SSLVPN interface or service if SAML is enabled for SSLVPN logins," as SecurityOnline quotes. Those firewalls still need SonicOS 7.3.4-7013 or 8.2.3-8015, because the same update fixes CVE-2026-107154 and CVE-2026-107155, each CVSS 8.8, in the management interface.
Read the build at Home > Dashboard | System > General and the login type at Network > SSL VPN > Server Settings. Export System Logs as CSV and run grep -iE 'ssl ?vpn' "$D"/*.csv | grep -i login. Match each login against the identity provider's sign-in log; a VPN login with no sign-in there means treat it as a likely compromise and escalate.
SonicWall lists no workaround, according to BleepingComputer. The only stop-gap is switching SSL VPN off for the WAN zone in Network > SSL VPN > Server Settings, which cuts remote access until the upgrade. SonicWall's upgrade guide puts the reboot at 5–8 minutes.
Yes. The upgrade closes the SAML bypass but doesn't undo anything an attacker did with a session opened before it, and SonicWall has not shared when exploitation began, according to BleepingComputer. Review the oldest retained VPN logs against identity-provider sign-ins, and the Auditing Logs for new users.