Policy

SonicWall VPN with SAML sign-in? Check one version and one setting before Friday.

CISA added SonicWall CVE-2026-19868 to its exploited list on November 6, with a November 20 due date. A valid password for an older sign-in method can skip single sign-on and the MFA it enforces. SonicWall fixed it in SonicOS 7.3.4-7013 and 8.2.3-8015 and published a workaround on November 9.

Rows of servers in a data center
“We have MFA on the VPN” and “every way into the VPN needs MFA” are different claims. Photo: Circuit & Capital

If your business uses a SonicWall firewall for remote access, and staff sign in to the SSL VPN through a single sign-on page (SAML), there is one version to check and one setting to understand before Friday, November 20, 2026. That is the federal due date CISA set when it added SonicWall CVE-2026-19868 to its Known Exploited Vulnerabilities catalog on November 6.

The flaw does not let a stranger in with no password. It lets someone who already holds a valid password for an older sign-in method skip the single sign-on step, and with it the multi-factor prompt that single sign-on was supposed to enforce. For a small firm, that is the difference between “we have MFA on the VPN” and “every route into the VPN needs MFA.” Those are not the same claim, and insurers increasingly ask about the second one.

What happened

SonicWall’s security advisory SNWLID-2026-0014, “SonicWall SonicOS Affected By Multiple Vulnerabilities,” covers seven CVEs in SonicOS, the operating system on its Gen7 and Gen8 firewalls. Its revision history dates version 1.0 to November 5 and version 1.1 to November 9. The CVE record for CVE-2026-19868 was published on November 6.

SonicWall describes CVE-2026-19868 as an authentication enforcement flaw in the SonicOS SSL VPN service that “may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls,” and says successful exploitation “may also bypass SAML-enforced multi-factor authentication (MFA).” In plain terms: if the firewall still accepts logins checked against LDAP, RADIUS, TACACS+ or similar servers, a valid password from one of those may get a user past the SAML page.

Two details in the advisory matter most. First, SonicWall says the flaw affects the SSL VPN “ONLY” when SAML is enabled for SSL VPN logins. Second, it says its security team “has investigated a report indicating potential exploitation” and urges customers to upgrade as soon as possible. SonicWall scores the flaw 7.1 (High). CISA added it to the catalog on the same day the CVE was published, with a November 20 due date for federal agencies. CISA lists known ransomware use as unknown.

Which firewalls, and which builds fix it

We read the affected and fixed versions from SonicWall’s advisory on November 18:

  • Gen7 hardware (TZ 270, 370, 470, 570 and 670 series, NSa 2700 to 6700, NSsp 10700 to 15700) and Gen7 NSv virtual firewalls (NSv 270, 470, 870): affected on 7.3.3-7015 and older, fixed in 7.3.4-7013 and higher.
  • Gen8 hardware (TZ 80, 280, 380, 480, 580 and 680 series, NSa 2800 to 5800) and Gen8 NSv (XS, S, M, L): affected on 8.2.2-8015 and older, fixed in 8.2.3-8015 and higher.

The advisory lists Gen7 and Gen8 SonicOS platforms only. If you run an older or different SonicWall product, check the advisory and SonicWall’s support pages for your exact model rather than assuming either way.

The same advisory also fixes six other SonicOS flaws, including two in the management interface that SonicWall scores 8.8 and a pre-authentication heap overflow in the SSL VPN service that can crash it (7.5). Those are not on CISA’s catalog, but the upgrade that fixes CVE-2026-19868 is the natural time to close them too.

If you cannot upgrade by Friday

Version 1.1 of the advisory, dated November 9, added a workaround. If SAML is in use and upgrading is not possible, SonicWall says to disable or delete any active LDAP, RADIUS and TACACS+ authentication servers configured on the firewall. It gives the menu path for each, under Device, Users, Settings, Authentication. Before you switch them off, find out what else relies on those servers, such as admin logins or Wi-Fi authentication, so the workaround does not lock out the people who need to finish the upgrade.

What it means for CFOs and CISOs

The lesson here is broader than one firewall. Many firms turned on single sign-on with MFA for the VPN and left the older sign-in methods configured “just in case.” Every one of those is a second door. When a cyber insurance form or a client security questionnaire asks whether MFA is required for all remote access, the honest answer depends on the doors you forgot, not the one you built.

There is also a budget point. A firewall that is out of support, or whose subscription has lapsed, may not be able to take the fixed build at all. If that is your situation, the cost of this week is not an hour of IT time; it is a replacement you may have been deferring. Better to learn that now, on your own schedule, than during an incident.

Finally, this is a vendor-management question for most small firms. If an IT provider runs your firewall, the patch is theirs to apply and the evidence is yours to keep. A dated, written answer is worth more than a verbal “we’re on it.”

What to do this week

  1. Find out if this applies. Ask whoever manages your network two questions: do we have a SonicWall Gen7 or Gen8 firewall, and does its SSL VPN use SAML single sign-on? If either answer is no, note it and move on.
  2. Check the SonicOS version. It should read 7.3.4-7013 or later on Gen7, or 8.2.3-8015 or later on Gen8. If not, schedule the upgrade before Friday. SonicWall’s advisory is the place to confirm the fixed build for your model.
  3. Apply the workaround if the upgrade slips. Disable or delete active LDAP, RADIUS and TACACS+ servers on the firewall, after checking what depends on them.
  4. Compare logins for the days your logs still cover. Every SSL VPN session should line up with a sign-in at your identity provider. A VPN session with no matching single sign-on record is worth a closer look.
  5. Write it down. Record the model, the version before and after, the date and who did the work. If the upgrade cannot happen this week, log it with a date and an owner in our free risk exception register. If anything looks wrong in the logs, our first 30 minutes guide covers what to do first.

What to watch next

  • SonicWall’s advisory. It says SonicWall investigated a report of potential exploitation but gives no detail. Watch for a revision that adds indicators or changes the workaround.
  • CISA’s catalog entry. The due date binds federal agencies, but it is a useful outside deadline for everyone else.
  • Insurance renewals. Expect more questions about whether MFA covers every remote-access path. Have your answer, and the date you checked, ready.

Not sure whether your VPN uses SAML, or which build you are on? Our $49 Am I Affected? Check reads the advisory against what you run and replies within 1 business day with a plain answer and 3 to 5 steps. For a single narrower question, such as how to word the request to your IT provider, our $29 Quick Answer covers it in writing.

Sources

Related: reading CISA’s due dates, the BeyondTrust remote support zero-day, ScreenConnect and your IT provider, and Security and vulnerabilities, every security briefing, guide and tool in one place.

ES
Emilio Santos edits Circuit & Capital. How we source and correct pieces: editorial standards.