Skip to content

SonicWall CVE-2026-19868: Patch the Exploited SSLVPN SAML/MFA Bypass

CVE-2026-19868 lets alternate SonicOS SSLVPN credentials bypass SAML and MFA. CISA lists it as exploited. Upgrade Gen7 to 7.3.4-7013 and Gen8 to 8.2.3-8015.

MGMCSA Guru Team November 16, 2026 7 min read
Fortress-like network gateway in a dim server room with a broken padlock on a side badge reader and a VPN tunnel of light, slate and amber

CVE-2026-19868 is an authentication enforcement flaw in the SonicOS SSLVPN service. SonicWall says a user with valid credentials for an alternate authentication method may be able to bypass SAML authentication controls on the SSLVPN, and that successful exploitation may also bypass the multi-factor authentication (MFA) that SAML enforces. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on November 6, 2026.

The flaw only matters on firewalls where SAML is enabled for SSLVPN logins. SonicWall’s advisory says that plainly. If you moved VPN sign-in to your identity provider to get MFA, patch CVE-2026-19868 first: Gen7 to 7.3.4-7013 or higher, and Gen8 to 8.2.3-8015 or higher. SonicWall lists no workaround.

This is not an unauthenticated takeover. The attacker needs valid credentials for another authentication method. The risk is that those credentials get past the SAML and MFA step you put in front of the VPN.

What CVE-2026-19868 does

SonicWall’s advisory SNWLID-2026-0014 describes the bug as an “SSLVPN Authentication Enforcement Vulnerability via Alternate Authentication Methods”. The weakness is classed as CWE-308, use of single-factor authentication.

A SonicOS firewall can accept SSLVPN logins through SAML, where the identity provider (IdP) handles sign-in and MFA. The same firewall may still have other authentication methods for SSLVPN users. CVE-2026-19868 lets a user with valid credentials for one of those alternate methods get past the SAML controls. If MFA is enforced only through SAML, that MFA step is skipped too.

SonicWall hasn’t published which alternate methods are involved. The advisory also says SonicWall PSIRT “has investigated a report indicating potential exploitation” and strongly urges customers to upgrade as soon as possible.

CVE-2026-19868 at a glance

Product SonicOS SSLVPN (Gen7 and Gen8)
Condition Only when SAML is enabled for SSLVPN logins
Weakness CWE-308: Use of single-factor authentication
SonicWall CVSS 3.1 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N)
CISA ADP CVSS 3.1 7.5 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N)
CISA KEV Added November 6, 2026; federal due date November 20, 2026
Known ransomware use Unknown (CISA)
Workaround None (SonicWall)

The two CVSS scores differ on one point. SonicWall scores privileges required as Low, because the attacker needs valid credentials. CISA’s ADP score, shown in the CVE record and NVD, scores it as None. NVD itself lists the CVE as Analyzed as of November 9, 2026, still with no NIST score of its own. The 8.8 headline score on the advisory belongs to two other CVEs in the same bundle.

Affected and fixed SonicOS versions

SonicWall’s advisory lists these platforms and versions:

PlatformModelsAffectedFixed
Gen7 hardwareTZ 270, 270W, 370, 370W, 470, 470W, 570, 570W, 570P, 670; NSa 2700, 3700, 4700, 5700, 6700; NSsp 10700, 11700, 13700, 157007.3.3-7015 and older7.3.4-7013 and higher
Gen7 NSvNSv 270, 470, 870 (ESX, KVM, Hyper-V, AWS, Azure)7.3.3-7015 and older7.3.4-7013 and higher
Gen8 hardwareTZ 80, 280, 280W, 380, 380W, 480, 580, 680; NSa 2800, 3800, 4800, 58008.2.2-8015 and older8.2.3-8015 and higher
Gen8 NSvNSv XS, S, M, L (ESX, KVM, Hyper-V, AWS, Azure)8.2.2-8015 and older8.2.3-8015 and higher

Patch CVE-2026-19868: the order of work

  1. Inventory every SonicOS firewall, hardware and NSv, and record the firmware version. Flag Gen7 at 7.3.3-7015 or older and Gen8 at 8.2.2-8015 or older.
  2. Find the ones with SAML on SSLVPN. SonicWall says only those are exposed to CVE-2026-19868. Put them at the front of the queue.
  3. Upgrade. Gen7 goes to 7.3.4-7013 or higher, Gen8 to 8.2.3-8015 or higher. The same release fixes six other CVEs in the bundle (listed below), so devices without SAML on SSLVPN still need the upgrade.
  4. Confirm the running version on each device after the reboot, not only in your change ticket.
  5. Review SSLVPN logins from before the patch (next section). Upgrading closes the hole, but it doesn’t undo any access that already happened.

Until a device is patched, you can reduce the alternate SSLVPN authentication paths for users who are meant to sign in through SAML, and limit where the SSLVPN is reachable from. That’s our operational suggestion, not a SonicWall workaround. SonicWall hasn’t said it blocks the bug, so test it in a change window and don’t treat it as a substitute for the upgrade.

Check for misuse before you patched

SonicWall and CISA haven’t published indicators of compromise, attacker details or a first-exploitation date. What you can do is compare what the firewall saw with what the IdP saw.

  • Match SSLVPN logins against IdP sign-ins. For users who should only connect through SAML, every SSLVPN session should have a matching IdP sign-in and MFA event. A VPN session with no IdP record is the pattern to investigate. If your IdP is Microsoft Entra ID, the sign-in logs are where that MFA event shows up; our guide on enabling MFA for Microsoft 365 users covers where MFA is enforced.
  • Review local, LDAP and RADIUS accounts with SSLVPN access. Look for recently created or changed users and group memberships that grant VPN access.
  • Rotate credentials for any account with an SSLVPN login you can’t explain.

This is a hunting hypothesis built from SonicWall’s description, not a published detection. Finding nothing doesn’t prove a device was never touched.

CVE-2026-19868 response checklist

  • List all Gen7 and Gen8 firewalls and NSv instances with firmware versions
  • Mark devices with SAML enabled for SSLVPN logins
  • Upgrade Gen7 to 7.3.4-7013+ and Gen8 to 8.2.3-8015+
  • Verify the running firmware version after reboot
  • Compare SSLVPN sessions with IdP sign-in and MFA records
  • Review local, LDAP and RADIUS users with SSLVPN access
  • Rotate credentials for unexplained SSLVPN logins

The other six CVEs in SNWLID-2026-0014

The same advisory covers seven CVEs, and the same upgrade fixes all of them. SonicWall describes the others like this:

CVEIssue (SonicWall)CVSS
CVE-2026-107155Permissive cross-domain policy in the management interface8.8
CVE-2026-107154Session validation flaw in the management interface8.8
CVE-2026-82308Pre-authentication heap overflow in SSL-VPN, denial of service7.5
CVE-2026-77708Pre-authentication stack overflow in the TACACS+ client, denial of service5.9
CVE-2026-77709Pre-authentication heap overflow in the TACACS+ client, denial of service5.9
CVE-2026-19703Weak password hashing on virtual appliances5.2

SonicWall says both management-interface CVEs could, in specific conditions, let a remote unauthenticated attacker perform unauthorized operations. Limiting who can reach the management interface reduces that exposure while you schedule the upgrade, whatever your SAML setup is.

Timeline

  • November 6, 2026, 10:40 UTC: SonicWall publishes SNWLID-2026-0014.
  • November 6, 2026: CISA adds CVE-2026-19868 to KEV, with a due date of November 20, 2026 for US federal agencies.
  • November 6, 2026, 18:55 UTC: The CVE record lists the public date; NVD publishes the entry at 19:17 UTC.

The November 20 date is a deadline for US federal civilian agencies under CISA’s directive, not a general grace period. With exploitation reported, patch sooner if you can.

What to do now

CVE-2026-19868 turns SAML-based MFA on a SonicWall SSLVPN into a step an attacker with alternate credentials may be able to skip. If SAML is on for SSLVPN, upgrade to 7.3.4-7013 (Gen7) or 8.2.3-8015 (Gen8) first, then compare VPN logins with your IdP logs for the period before the patch. Firewalls without SAML on SSLVPN still need the same upgrade for the other six CVEs. For more patch walkthroughs, see all articles.

Frequently asked questions

Which SonicWall firewalls are affected by CVE-2026-19868?

SonicWall lists Gen7 hardware and NSv on SonicOS 7.3.3-7015 and older, and Gen8 hardware and NSv on 8.2.2-8015 and older. The flaw only affects the SSLVPN when SAML is enabled for SSLVPN logins.

Which SonicOS versions fix CVE-2026-19868?

Upgrade Gen7 to 7.3.4-7013 or higher and Gen8 to 8.2.3-8015 or higher. SonicWall says no workaround is available.

Is CVE-2026-19868 exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on November 6, 2026, and SonicWall says it investigated a report indicating potential exploitation. CISA lists known ransomware use as unknown, and no indicators of compromise have been published.

Can an unauthenticated attacker use CVE-2026-19868?

SonicWall describes it as needing valid credentials for an alternate authentication method, and scores privileges required as Low. CISA's ADP score treats privileges as None, which is why it scores 7.5 against SonicWall's 7.1.

Are Gen6 SonicWall firewalls affected?

The advisory doesn't list Gen6 as affected or fixed, and the CVE record leaves unlisted versions as unknown. Check with SonicWall for Gen6 rather than assuming it is safe.

Sources & further reading

Official vendor documentation referenced while writing this guide.

MG

MCSA Guru Team

IT & Systems Administration

We are working IT pros and system administrators who spend our days in Windows Server, Microsoft 365, and the wider Microsoft stack. MCSA Guru is where we write down the fixes and walkthroughs we wish we had found the first time.

MCSA Guru provides independent, educational IT guidance. Microsoft, Windows, Windows Server, Microsoft 365, Exchange, and Microsoft Teams are trademarks of Microsoft Corporation; Docker is a trademark of Docker, Inc. MCSA Guru is not affiliated with or endorsed by Microsoft or Docker. Always test changes in a safe environment before applying them in production.

Related guides

Fixing something right now?

Jump straight into the guide library or search for the exact error or task you are dealing with.