Skip to content
Log inRegister

SonicWall SonicOS SSL VPN Flaw CVE-2026-19868 Lets Valid Users Bypass SAML MFA: Patch Now

Dr. Abeer Alshammari · Published 11/8/2026

IntermediateProfessionalsCISOsExecutives
Developing story: CONFIRMED

CISA added CVE-2026-19868, an authentication enforcement flaw in the SonicOS SSL VPN, to its Known Exploited Vulnerabilities (KEV) catalog on 6 November 2026. SonicWall has released fixed builds, and there is no workaround.

What happened

On 6 November 2026 SonicWall published advisory SNWLID-2026-0014, which covers seven SonicOS vulnerabilities. One of them, CVE-2026-19868 (CVSS 7.1), affects the SSL VPN service when SAML based login is enabled. A user who holds valid credentials for an alternate authentication method can bypass the SAML authentication controls, which may also bypass multi-factor authentication enforced through SAML. SonicWall said its product security team investigated a report indicating potential exploitation, and CISA added the flaw to the KEV catalog the same day. Neither SonicWall nor CISA has shared details of the attacks, and it is not clear whether the flaw was used as a zero-day. Federal civilian agencies must secure affected systems by 20 November 2026.

Why it matters

SAML sign-in with MFA is often the control that organisations rely on to protect remote access. A flaw that lets a login route around that policy weakens the main barrier in front of the internal network. The attacker still needs valid credentials for some other method, so stolen or reused passwords become more valuable, not less.

Who is affected

Gen7 TZ, NSa, NSsp and NSv firewalls running SonicOS 7.3.3-7015 or older, and Gen8 TZ, NSa and NSv firewalls running SonicOS 8.2.2-8015 or older. According to the vendor, an SSL VPN is exposed only if SAML based login is enabled.

Technical impact

The weakness sits in how the SSL VPN enforces which authentication method a user must complete. A successful bypass may let a session be established without the SAML step, including the MFA challenge that SAML provides. The other six flaws in the same advisory are not marked as exploited by SonicWall.

Governance impact

This is a clear test of whether remote access MFA is verified or only assumed. Boards and risk owners should ask whether VPN authentication paths are inventoried, whether alternate login methods are still enabled without a business need, and whether edge device patching has a defined deadline. For regulated entities, an exploited edge device flaw with a public KEV entry will be read by auditors as a known and fixable exposure.

What security teams should do

Upgrade to SonicOS 7.3.4-7013 or 8.2.3-8015, as SonicWall offers no workaround. Check whether SAML login is enabled on the SSL VPN and whether alternate authentication methods are still active, and disable any that are not needed. Review SSL VPN logs for logins that did not pass through the identity provider, and rotate credentials for accounts with suspicious sessions. Treat the federal deadline of 20 November as a sensible target for all organisations.

What executives should know

An exploited flaw in a firewall VPN, with a fix available, should be patched within days, not at the next maintenance window. Ask your security lead to confirm in writing which firewalls are in scope, when they will be upgraded, and whether remote access logs have been reviewed.

Sources: BleepingComputer and SecurityWeek reporting on SonicWall advisory SNWLID-2026-0014 and the CISA KEV addition. The primary SonicWall and CISA pages could not be opened during verification, so details are taken from these two reports. Written by Dr. Abeer Alshammari.

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights