SonicWall SonicOS SSL VPN Flaw (CVE-2026-19868) Can Bypass SAML Authentication and Multi-Factor Checks
SonicWall patched a SonicOS SSL VPN flaw (CVE-2026-19868) that allows an authentication bypass when SAML login is enabled. CISA added it to its exploited list on 6 November. Which devices and versions are affected, and what to do?
In brief: SonicWall patched CVE-2026-19868 in the SonicOS SSL VPN service with advisory SNWLID-2026-0014 on 6 November 2026. According to SecurityWeek, a user with valid credentials for an alternate authentication method may bypass SAML controls, which may also bypass SAML-enforced multi-factor authentication (MFA). The CVSS score is 7.1 (high). The SSL VPN is affected only when SAML-based login is enabled. CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog the same day; the federal deadline is 20 November. Affected: SonicOS 7.3.3-7015 and older (Gen7 TZ, NSa, NSsp, NSv) and 8.2.2-8015 and older (Gen8 TZ, NSa, NSv). Fixed versions: 7.3.4-7013 and 8.2.3-8015. There is no workaround. This article is based on SecurityWeek's 7 November report.
Last updated: 9 November 2026
What happened?
SonicWall's advisory describes an authentication enforcement vulnerability in SonicOS's SSL VPN service. When SAML-based login is enabled, a user may be able to use valid credentials for a different authentication method to get around SAML controls, and that can defeat the MFA enforced through SAML too.
| Item | Detail |
|---|---|
| Identifier | CVE-2026-19868 (SonicWall advisory SNWLID-2026-0014) |
| Severity | CVSS 7.1 (high) |
| Component | SonicOS SSL VPN; exposed only when SAML-based login is enabled |
| Reported by | Ryan Harris, The Electronic Office |
| Published / KEV | 6 November 2026 (advisory and CISA KEV addition) |
| Federal deadline | 20 November 2026 (BOD 26-04; binding only for federal agencies) |
| Workaround | None; SonicWall strongly urges upgrading |
Which devices and versions are affected?
| Device family | Affected | Fixed |
|---|---|---|
| Gen7 TZ, NSa, NSsp, NSv | SonicOS 7.3.3-7015 and older | 7.3.4-7013 |
| Gen8 TZ, NSa, NSv | SonicOS 8.2.2-8015 and older | 8.2.3-8015 |
Exploitation status
SonicWall says its product security team investigated a report of potential exploitation. According to SecurityWeek, neither SonicWall nor CISA has shared details of the attacks, and it is unclear whether the flaw was used as a zero-day. Still, its entry in the KEV catalog means use has been demonstrated.
Other flaws in the same advisory
Not marked as exploited, but closed in the same update:
- Two management-interface flaws (CVSS 8.8): a permissive cross-domain policy issue and a session validation bug. Under some conditions a remote attacker may act without logging in.
- Three pre-authentication buffer overflows: in the SSL VPN service and the TACACS+ authentication client; they can cause application-level denial of service.
- Weak password hashing on virtual appliances: requires high-privileged local access and can expose a platform credential.
So it makes sense to move to a version that applies the whole advisory, not just CVE-2026-19868.
If you use SonicWall: 7 steps
- Identify your device and version: Gen7 or Gen8, and which SonicOS version.
- Is SAML-based SSL VPN login on? If not, exposure to this flaw is lower; upgrade anyway for the other fixes in the advisory.
- Upgrade: 7.3.4-7013 for Gen7, 8.2.3-8015 for Gen8, or later. There is no workaround.
- Review VPN logs: unexpected logins via non-SAML methods, unusual hours and geographies, sessions without an MFA prompt.
- End suspicious sessions and reset passwords and sessions for affected users.
- Don't leave the management interface exposed to the internet: limit management access to the internal network or to VPN/IP restrictions.
- Simplify authentication methods: keeping several methods enabled on the same VPN opens the door to this kind of bypass. Turn off the ones you don't use.
A broader lesson: MFA alone is not enough
MFA is a strong defence, but it assumes it is enforced correctly where it applies. This flaw shows that when the authentication layer is bypassed, MFA can be bypassed with it. Layer your defences:
- Give accounts that log in to the VPN least privilege; getting into the VPN should not mean getting into the whole network (network segmentation).
- Keep the authentication of your own internal systems (ERP, CRM, file servers).
- Set up anomalous-login alerts.
- Track the software of security appliances (firewalls, VPNs) as closely as your website; these devices are frequent targets.
For general application security see our 12 OWASP-focused measures. For prioritising patches, our October patch scorecard and patch management article help.
With Aktaş Digital
We are not a network security company; but we support authentication, authorisation and access design in business software and web applications. To have your applications' session and permission security reviewed, use our quote form. Related services: web applications and CRM systems.
Frequently Asked Questions
I don't use SAML. Am I affected?
According to SonicWall, the SSL VPN is exposed to this flaw only when SAML-based login is enabled. If you don't use SAML, your exposure is lower; upgrading is still recommended for the other fixes in the advisory.
Is there a workaround?
No. SonicWall states there are no workarounds and strongly urges upgrading to the fixed releases.
Does exploiting it require a valid account?
Yes: the report describes the attacker as a user with valid credentials for an alternate authentication method. That makes stolen or leaked accounts even more valuable with this flaw.
Is CISA's deadline binding for me?
No; BOD 26-04 binds only US federal civilian agencies. Still, CISA's KEV list is a reliable signal that exploitation is real.
Are other vendors' firewalls affected?
This report covers only SonicWall SonicOS. Follow your own security appliance vendor's advisories separately.
Conclusion
CVE-2026-19868 shows that authentication and MFA on SAML-protected SSL VPNs can be bypassed, and exploitation has been reported. Move to SonicOS 7.3.4-7013 or 8.2.3-8015, review your VPN logs and limit network access to least privilege. The first step: ask whoever runs your IT for your device model and SonicOS version in writing.
