OFFSEC · Offensive Security

SonicOS SAML bypass shows MFA fails through the side door

CVE-2026-19868 lets a valid password skip SAML-enforced MFA on SonicWall SSL-VPN. It is exploited, on CISA's KEV list, and has no workaround.

MFA is only as strong as the weakest login path

SonicWall has fixed an actively exploited flaw that lets an attacker holding a valid password skip SAML-enforced multi-factor authentication on SonicOS SSL-VPN [3][5]. The bug, CVE-2026-19868, affects Gen 7 and Gen 8 physical and virtual firewalls, but only where SAML is enabled for SSL-VPN logins [4][6]. SonicWall lists no workaround [3][4]. The lesson for defenders is wider than one patch. An organisation that moved its VPN to SAML single sign-on to get MFA can still be exposed through a second, older authentication route that the gateway continues to honour.

This is not an unauthenticated bypass. The attacker needs valid credentials for an alternate authentication method [5][7]. That bar is low in practice. Valid credentials, brute-forced or reused from earlier compromises, were the starting point in the SonicWall SSL-VPN intrusions documented by ReliaQuest and Arctic Wolf [12][13].

What the advisory and the data say

SonicWall published advisory SNWLID-2026-0014 on 6 November 2026. It covers seven vulnerabilities, of which only CVE-2026-19868 is marked as exploited [4][8]. SonicWall PSIRT said it had “investigated a report indicating potential exploitation” but shared no attack details [5]. CISA added the flaw to its Known Exploited Vulnerabilities catalogue the same day, with a 20 November remediation deadline for US federal civilian agencies [2][5]. Canada’s Cyber Centre issued its own advisory on 6 November [2]. The flaw was reported by Ryan Harris of The Electronic Office [3][4].

The weakness is classified as CWE-308, use of single-factor authentication [6][8]. MITRE’s guidance for that class is to require multiple independent authentication schemes where several are possible [11]. Ostorlab’s reading of the advisory is that the gateway does not enforce the SAML policy for accounts that can also log in by another method, so a credential for that method completes the login without SAML or its MFA [6]. SonicWall has not published code-level detail, so the exact path is not public [6].

  • Affected: Gen 7 TZ, NSa, NSsp and NSv on SonicOS 7.3.3-7015 and older; Gen 8 TZ, NSa and NSv on 8.2.2-8015 and older [4].
  • Fixed: 7.3.4-7013 or later for Gen 7, and 8.2.3-8015 for Gen 8 [1][3].
  • Gen 6 is not listed as affected but is end-of-support; SonicWall advises moving to Gen 8 [1][5].
  • Companion fixes: two management-interface flaws rated 8.8 that may be abused without login under certain conditions, three pre-authentication overflows in SSL-VPN and the TACACS+ client with denial-of-service impact, and a weak password hash on virtual appliances [4][8].

Where the sources differ

The severity score is not settled. SonicWall rates the flaw CVSS 7.1 [3][4]. Ostorlab reports a CISA ADP score of 7.5 [6], and Security Affairs uses 7.5 [7]. Two articles carry both figures in different places [8][10]. Defenders should treat the KEV listing, not the base score, as the prioritisation signal.

Version statements also diverge. SonicWall’s advisory lists Gen 8 8.2.2-8015 itself as affected [1][4]. The Canadian advisory describes affected releases as those earlier than 8.2.2-8015, which would exclude that build [2]. The vendor text should govern. SonicWall’s own notice is also internally inconsistent on timing: its introduction says fixes were scheduled for 5 and 6 November, while its version table shows 7.3.4-7013 available from 20 October [1]. Gen 7 sites that applied 7.3.4 in October may already be on a fixed build; they should confirm against the advisory rather than assume.

Whether this was a zero-day is unclear. SecurityWeek reports that neither SonicWall nor CISA has said so [4]. Aviatrix states it was exploited before a patch existed but gives no evidence [10]. No security firm has yet published an incident analysis, and no indicators of compromise have been released [5]. Reports differ on the governing directive: SecurityWeek cites BOD 26-04 [4], Security Affairs cites BOD 22-01 [7]. The 20 November deadline is the same in both.

Why it matters: a recurring pattern

CVE-2026-19868 is the latest in a run of SonicWall SSL-VPN MFA failures. ReliaQuest assessed with medium confidence that CVE-2024-12802, a separate MFA bypass rooted in inconsistent MFA coverage across Active Directory login formats, was exploited in February and March 2026 [12]. Some intrusions needed as few as 13 credential attempts, and the bypass raised no failed-MFA alert [12]. ReliaQuest also found that on Gen 6 the firmware patch alone did not close the hole without manual reconfiguration [12].

In 2025 Arctic Wolf documented Akira ransomware intrusions through SonicWall SSL-VPN on accounts with OTP MFA enabled, with encryption in under four hours in almost all cases [13]. It could not fully explain how MFA was passed and concluded the evidence pointed to valid credentials [13]. Rapid7 linked the same activity to over-permissive default LDAP group settings and an exposed portal that allowed attackers to enrol their own TOTP device [14]. Notably, Arctic Wolf recommended moving VPN authentication to SSO or SAML, which it had not seen abused [13]. CVE-2026-19868 shows that SAML helps only if it is the sole path.

Reconnaissance is constant. GreyNoise recorded 84,142 scanning sessions against SonicOS from 4,305 source IPs over four days in February 2026, about 92% of them checking whether SSL-VPN was enabled [15]. SonicWall’s SMA1000 line saw exploitation attempts against CVE-2026-102255 within two days of its October disclosure [16]. Exposure windows for SonicWall edge devices are measured in days.

What to do

  • Upgrade Gen 7 to 7.3.4-7013 or later and Gen 8 to 8.2.3-8015 now; there is no workaround [1][3].
  • Until patched, remove or disable non-SAML access for SSL-VPN accounts and restrict SSL-VPN to trusted source ranges, keeping an administrative path that does not depend on the VPN [6].
  • Hunt for SSL-VPN logins that succeeded without a matching sign-in and MFA event in the identity provider’s logs [5]. Check for SAML-only users authenticating by another method [6].
  • Reset credentials for any account that logged in that way and review what those sessions reached [5]. Where firmware was ever vulnerable to earlier SSL-VPN flaws, reset local, LDAP-sync and OTP secrets as well [13][14].
  • After patching, confirm that MFA applies to every authentication route the gateway accepts, not only the primary one [9].
  • Forward SonicWall authentication logs to a SIEM and restrict management interfaces and API paths to administrative addresses [12][15].
  • Plan the retirement of Gen 6 appliances, which no longer receive fixes [1][12].

Offensive security close

For red teams and assessors, this flaw belongs in the identity layer of a test scope, not only the patch audit. The question to ask of any remote-access gateway is how many authentication methods it will accept for one user, and whether each carries the same MFA policy. Edge-device MFA has failed through credential reuse, enrolment abuse, format mismatches and now policy enforcement gaps [12][13][14].

Sources

Every R3KONX article cites its primary material. 16 sources, in order of first citation. Links open the original publication.

  1. SonicOS 7.3.4 and 8.2.3 Security Advisory - Gen 7 and Gen 8 Firewalls SonicWall · 2026-11-06
  2. SonicWall security advisory (AV26-1133) Canadian Centre for Cyber Security · 2026-11-06
  3. SonicWall warns of new SSL-VPN MFA bypass flaw exploited in attacks BleepingComputer · 2026-11-06
  4. SonicWall Patches Exploited SonicOS Vulnerability That Weakens VPN Logins SecurityWeek · 2026-11-07
  5. Exploited SonicWall SSL-VPN flaw lets attackers bypass SAML-enforced MFA (CVE-2026-19868) Help Net Security · 2026-11-09
  6. SonicWall SSLVPN SAML Bypass, Exploited in the Wild (CVE-2026-19868) Ostorlab · 2026-11-07
  7. U.S. CISA adds SonicWall SonicOS SSLVPN flaw to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-11-07
  8. Attackers Exploit SonicWall SonicOS SSLVPN Flaw CVE-2026-19868 in the Wild Daily CyberSecurity (SecurityOnline) · 2026-11-06
  9. CISA Warns of SonicWall SonicOS SSLVPN Vulnerability Exploited in Attacks Cyber Security News · 2026-11-09
  10. SonicWall CVE-2026-19868 SSL-VPN MFA Bypass Exploited Aviatrix Threat Research Center · 2026-11-07
  11. CWE-308: Use of Single-factor Authentication MITRE · 2026
  12. Threat Spotlight: VPN Exploitation - When Patched Doesn't Mean Protected ReliaQuest · 2026-05-19
  13. Smash and Grab: Aggressive Akira Campaign Targets SonicWall VPNs Arctic Wolf Labs · 2025-09-26
  14. Akira ransomware group utilizing SonicWall devices for initial access Rapid7 · 2025-09-10
  15. Active reconnaissance campaign targets SonicWall firewalls through commercial proxy infrastructure GreyNoise · 2026-02-27
  16. Critical SonicWall vulnerability exploited days after disclosure SecurityWeek · 2026-10-12

Researched and written by the R3KONX Analysis Desk from the cited primary material. SonicWall's PSIRT advisory page (SNWLID-2026-0014) and CISA's KEV alert could not be retrieved; the advisory is cited via SonicWall's support notice and trade reporting, and the KEV addition via the Canadian Centre for Cyber Security and trade reporting. No incident analysis or indicators had been published at the time of writing. Corrections: event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.