Security Digest · Nov 6, 2026 · Vulnerability · Network edge
SonicWall SSLVPN SAML/MFA Bypass CVE-2026-19868 (KEV)
Exploited SonicOS SSLVPN flaw lets a valid non-SAML login skip SAML-enforced MFA. Fixed in 7.3.4-7013 and 8.2.3-8015; act now if SAML is on.
Our verdict
Act now
If your SonicWall firewall uses SAML for SSLVPN logins, upgrade SonicOS now, because exploitation is confirmed and MFA through your identity provider does not protect you; if SAML is not enabled for SSLVPN, this CVE does not apply, but the same upgrade fixes six other flaws and belongs in this week's patching.
Who must act: Admins of Gen7 (SonicOS 7.3.3-7015 or earlier) and Gen8 (8.2.2-8015 or earlier) TZ, NSa, NSsp and NSv firewalls with SAML enabled for SSLVPN logins.
Who can relax: Sites with no SSLVPN service, SSLVPN without SAML, or firewalls already on 7.3.4-7013 / 8.2.3-8015 or later; SMA100 and SMA1000 appliances are separate products and not listed.
- Affected
- SonicOS Gen7 (TZ, NSa, NSsp, NSv) 7.3.3-7015 and earlier
SonicOS Gen8 (TZ, NSa, NSv) 8.2.2-8015 and earlier
Only when SAML is enabled for SSLVPN logins - Fixed in
- SonicOS 7.3.4-7013 and later (Gen7)
SonicOS 8.2.3-8015 and later (Gen8) - CVSS
- 7.1 (v3.1, vendor)
- EPSS
- 8.0% (percentile 95)
- CISA KEV
- Yes, listed as known exploited
- Exploitation
- Exploited in the wild
- Severity
- High
What to do
- Check each firewall's SonicOS version and whether SAML is enabled for SSLVPN logins.
- Upgrade Gen7 units to SonicOS 7.3.4-7013 or later and Gen8 units to 8.2.3-8015 or later.
- Until upgraded, remove or disable SSLVPN-capable accounts that can sign in through a non-SAML method (local, LDAP, RADIUS and similar), keeping a separate admin path.
- Restrict the SSLVPN portal to known source addresses where your user base allows it.
- Review at least the last 30 days of SSLVPN logins and reset credentials for any account with an unexplained non-SAML session.
- Patch firewalls without SAML in the same window; the release also fixes six other SonicOS flaws, including two rated 8.8.
How to check if you are affected or compromised
- Search SSLVPN authentication logs (on the firewall or in your SIEM) for successful logins by users who should only authenticate through SAML but show a different authentication method.
- Correlate SSLVPN sessions with your identity provider's sign-in log: a VPN session with no matching IdP sign-in or MFA event is suspicious.
- Look for new local users, newly enabled authentication methods or new SSLVPN group memberships on the firewall.
- For any suspect session, review the source address, duration and internal hosts reached, and preserve logs before rebooting or upgrading.
What happened#
On November 6, 2026, SonicWall published advisory SNWLID-2026-0014, covering seven SonicOS vulnerabilities fixed in new firmware. The one that matters most is CVE-2026-19868, an authentication enforcement flaw (CWE-308, use of single-factor authentication) in the SSLVPN service. In the words of the CVE record, it "may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls. Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA)."
The same day, CISA added the CVE to the Known Exploited Vulnerabilities catalog. Under BOD 26-04, federal agencies must remediate by November 20. According to BleepingComputer, SonicWall's advisory says "SonicWall PSIRT has investigated a report indicating potential exploitation of this vulnerability." No victims, actors, indicators or exploit details have been published. BleepingComputer credits Ryan Harris of The Electronic Office with reporting the bug.
SonicWall scores the flaw CVSS 3.1 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N), as reported by Ostorlab and GBHackers. CISA's ADP entry in the record and on NVD gives 7.5 with PR:N. The difference is only whether the attacker's valid password counts as a privilege. We could not render SonicWall's advisory page directly, so the fixed versions below come from the CVE record plus three independent write-ups that agree with each other.
Who is affected#
According to the CVE record, affected versions are SonicOS 7.3.3-7015 and older (Gen7) and 8.2.2-8015 and older (Gen8). Coverage of the advisory lists Gen7 TZ, NSa and NSsp hardware and NSv virtual firewalls, plus Gen8 TZ, NSa and NSv. Fixes are in SonicOS 7.3.4-7013 for Gen7 and 8.2.3-8015 for Gen8. The Gen7 fix is a newer minor release (7.3.4) even though its build number is lower than the last vulnerable 7.3.3 build. SonicWall lists no workaround.
The key condition: per the advisory as quoted by Ostorlab, the flaw "ONLY impacts the SonicOS SSLVPN interface or service if SAML is enabled for SSLVPN logins." The SMA100 and SMA1000 secure-access appliances are separate product lines and are not in this advisory.
Do you really need to act?#
If you enabled SAML for SSLVPN, yes. Most organizations turn on SAML to put VPN access behind their identity provider's MFA. This bug undoes that: anyone with a working password for a second authentication path on the firewall can get in without the IdP or its MFA prompt. As of November 7, 2026, the advisory does not say which alternate methods are affected, such as local users, LDAP or RADIUS. Stolen or reused VPN passwords are common, and SonicWall remote-access products have been a frequent target this year. BleepingComputer lists SMA1000 zero-days exploited in July and September and exploitation attempts in October. Combined with the KEV listing, that makes this an act-now patch for SAML users, even though the CVSS score is only high.
The attacker still needs valid credentials, so this is not an unauthenticated takeover, and no public proof of concept exists. If SAML is not enabled for SSLVPN, CVE-2026-19868 does not apply to you. The same firmware still fixes two 8.8-rated management-interface flaws (CVE-2026-107155, CVE-2026-107154), pre-auth overflows in SSLVPN (CVE-2026-82308) and the TACACS+ client (CVE-2026-77708, CVE-2026-77709), and weak password hashing on virtual appliances (CVE-2026-19703). None of those is reported as exploited, so a normal this-week upgrade is reasonable for those firewalls.
What to do now#
- Inventory SonicWall firewalls and versions. The version is on the management dashboard, or run
show versionon the SonicOS CLI. Note which units have SAML enabled for SSLVPN. - Upgrade Gen7 units to 7.3.4-7013 or later and Gen8 units to 8.2.3-8015 or later. Take a configuration backup first.
- Until a unit is upgraded, shrink the bypass path. Disable or remove SSLVPN-capable accounts that can authenticate without SAML, such as local accounts and LDAP or RADIUS-backed users. Keep a separate administrative path so you do not lock yourself out.
- Where practical, restrict the SSLVPN portal to known source ranges or countries.
- Review recent SSLVPN logins, as described below, and reset passwords for any account with an unexplained session.
- Schedule the same upgrade for non-SAML firewalls this week to pick up the six companion fixes.
How to tell if you were hit#
SonicWall has published no indicators of compromise as of November 7, 2026. The useful signal is a mismatch between authentication methods. A user who should only reach the VPN through SAML has a successful SSLVPN login recorded under another method, or has a VPN session with no matching sign-in and MFA event in your identity provider's log. Export SSLVPN authentication events from the firewall or your syslog/SIEM and compare them against IdP sign-ins for the same users and times. Also check for new local users, newly enabled authentication methods or changed SSLVPN group memberships. For any suspicious session, record the source address and the internal hosts it reached, and preserve the logs before upgrading. CISA's BOD 26-04 also points federal agencies to forensic triage guidance. Treat a confirmed bypass as a breach of the internal network, not just of one account.
Timeline#
- — SonicWall publishes SNWLID-2026-0014 and fixed SonicOS 7.3.4-7013 / 8.2.3-8015, noting a report of potential exploitation. CVE-2026-19868 is published.
- — CISA adds CVE-2026-19868 to the KEV catalog with a November 20 federal deadline.
- — No public exploit, victim list or indicators have been released.
- — BOD 26-04 remediation deadline for federal civilian agencies.
Vulnerability records
- CVE-2026-19868 · KEV 2026-11-06 · An authentication enforcement vulnerability in SonicOS SSLVPN service may allow a user with valid credentials for an alternate authentication method to bypass…
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- SonicWall PSIRT — SNWLID-2026-0014: SonicOS multiple vulnerabilities psirt.global.sonicwall.com
- CVE record — CVE-2026-19868 cve.org
- NVD — CVE-2026-19868 nvd.nist.gov
- CISA — Known Exploited Vulnerabilities: CVE-2026-19868 cisa.gov
- CISA — BOD 26-04: Prioritizing Security Updates Based on Risk cisa.gov
- Ostorlab — SonicWall SSLVPN SAML Bypass, Exploited in the Wild (CVE-2026-19868) blog.ostorlab.co