SonicWall CVE-2026-19868 turns SAML-protected VPN logins back into passwords
An exploited SonicOS SSLVPN flaw lets holders of a working local, LDAP or RADIUS credential skip SAML and its MFA. Patching closes it; only credential hygiene and log review tell you whether it was used.
CVE-2026-19868 does not let an attacker in without a password. It removes the second factor from anyone who already has one. On SonicOS firewalls with SAML enabled for SSLVPN logins, a user holding valid credentials for an alternate authentication method can bypass SAML controls, including SAML-enforced multi-factor authentication [1][3]. SonicWall says it has investigated a report of potential exploitation, and CISA added the flaw to its Known Exploited Vulnerabilities catalog on 6 November 2026, the day advisory SNWLID-2026-0014 was published [1][2]. The patch closes the hole. It does not tell you whether someone has already walked through it.
What the record says
- Weakness: CWE-308, use of single-factor authentication, which MITRE defines as relying on a single factor such as a password where the security context calls for more [4][9].
- Exposure: only the SSLVPN interface or service, and only where SAML is enabled for SSLVPN logins [1][5]. Deployments without SAML on SSLVPN are not exposed to this CVE, though the same bulletin fixes six other SonicOS flaws [1][6].
- Affected: Gen7 TZ, NSa, NSsp and NSv on 7.3.3-7015 and older; Gen8 TZ, NSa and NSv on 8.2.2-8015 and older [1][4].
- Fixed: 7.3.4-7013 for Gen7 and 8.2.3-8015 for Gen8, per SecurityWeek, Ostorlab and nFlo [1][5][6]. SonicWall lists no workaround [1].
- KEV: added 6 November, due 20 November for US federal civilian agencies. The required action is to apply vendor mitigations, perform forensic triage, or discontinue use of the product [3]. CISA’s SSVC entry records exploitation as active, not automatable, with partial technical impact [4].
- Reporter: Ryan Harris of The Electronic Office [1].
Two points in the record need care. First, severity. SonicWall scores the flaw 7.1 with privileges required set to low; the CISA-ADP entry in the CVE and NVD records scores it 7.5 with privileges required set to none [3][4][5][6]. Both vectors keep attack complexity high. One secondary write-up says the 7.5 figure belonged to a different flaw in the bulletin [8]. The published CVE record contradicts that; the 7.5 score is attached to CVE-2026-19868 itself [4]. The vendor’s own low-privilege scoring matches what the bug is, since the attacker must hold a working credential.
Second, the fixed builds. nFlo flagged that the Gen7 fix (build 7013) carries a lower build number than the affected bound (7015), and that the Gen8 fixed and affected builds share the suffix 8015 [6]. Read as release numbers, there is no contradiction: 7.3.4 follows 7.3.3 and 8.2.3 follows 8.2.2, and the build suffix is not a cross-release counter. The CVE record lists only affected ranges [4], OffSeq’s fixed-in field is blank [7], and SonicWall’s advisory page did not render for us. Three secondary sources agree on the fixed builds [1][5][6]. Confirm them against the PSIRT bulletin before closing the ticket, and treat any build on the 7.3.3 or 8.2.2 trains as unpatched.
What it means
Where SSLVPN is set to SAML, the intended design is that the portal sends the user to the identity provider and no password is entered at the firewall [10]. The flaw breaks that assumption. Ostorlab’s reading is that the gateway does not enforce the SAML policy for accounts that can still authenticate by another method, so a session completes without any SAML assertion [5]. SonicWall has not published the code path or which alternate method is involved [5]. The practical consequence is the same either way. Any local, LDAP or RADIUS credential that still works against the SSLVPN is now a single-factor credential.
That matters because of where SonicWall SSLVPN credentials have been going for the past year. In August 2025 SonicWall attributed a wave of Gen7 SSLVPN intrusions to CVE-2024-40766 and to local passwords carried over in Gen6-to-Gen7 migrations and never reset, and said it was investigating fewer than 40 incidents [11]. Arctic Wolf and Huntress linked that activity to Akira ransomware, according to Tenable [13]. Arctic Wolf reported Akira logins to accounts with OTP MFA enabled, using credentials it assessed were likely exfiltrated earlier through CVE-2024-40766. It also saw logins against LDAP synchronisation accounts never meant for VPN use [12]. Canada’s Cyber Centre carried the same guidance at the time [14]. Separately, SonicWall’s investigation with Mandiant found that an unauthorised party accessed firewall configuration backups for all customers of its MySonicWall cloud backup service. Secrets in those files are individually encrypted, but SonicWall warned that possession of them could increase the risk of targeted attacks [15]. Arctic Wolf found no evidence linking that incident to the Akira campaign [12].
None of the sources links CVE-2026-19868 to Akira or to those earlier credential sets. SonicWall and CISA have shared no actor, campaign or victim detail, and the KEV entry lists known ransomware use as unknown [1][8]. What the history shows is a population of SonicWall SSLVPN credentials that may already be outside their owners’ control. This bug lowers the bar for using them. The appliance line also remains a steady target. SecurityWeek counts 20 SonicWall entries in KEV [1], and the Cyber Centre reported exploitation of SMA1000 flaws in September and October 2026 [16][17].
Risk scoring may understate this. OffSeq lists an EPSS probability of 0.6 per cent and no public exploit code [7]. Neither tells you how many working VPN passwords for your users already sit with someone else.
What to do
- Patch to 7.3.4-7013 or 8.2.3-8015, or later, after confirming the builds against the vendor bulletin [5][6]. For NSv, Ostorlab notes that restoring a configuration onto an old image brings the flaw back [5].
- Inventory alternate authentication paths into SSLVPN. Remove or disable local, LDAP and RADIUS methods that SAML users do not need, and keep an administrative path that does not depend on SSLVPN [5][6].
- Until patched, restrict SSLVPN to known source addresses, or take internet-facing SSLVPN offline where the business allows [5][6].
- Hunt backwards. Look for successful SSLVPN logins by SAML-only accounts that recorded a non-SAML method, and for VPN sessions with no matching identity provider sign-in. Check source addresses, times and internal destinations against each account’s normal pattern [5][6].
- Review account changes over the same window: new local accounts, newly enabled alternate methods and new SSLVPN authorisations [5].
- After upgrading, reset passwords for accounts with alternate login methods and terminate active VPN sessions [6]. Where devices are older or were migrated, apply SonicWall’s earlier advice: reset local SSLVPN passwords, rotate the LDAP bind credential, and review LDAP SSLVPN default user groups [11]. Arctic Wolf adds OTP MFA secrets and LDAP synchronisation accounts to that list [12].
- If a login cannot be ruled out, treat the account as compromised and scope what it could reach [5].
“Customers are strongly urged to upgrade to the latest release as soon as possible to mitigate the associated risks.” — SonicWall, SNWLID-2026-0014, as quoted by Security Affairs [2]
The offensive-security reading
For red teams and assessors, this is a reminder to test the authentication policy as enforced, not as configured. A SAML setting on the portal page is a claim about one login path. The question an assessor should ask is whether any other path still accepts a password, and whether the logs would show it. SonicWall’s fix closes one such path in SSLVPN [1]. The broader control is to remove every credential that can authenticate outside the identity provider, then watch for any login that did.
Sources
Every R3KONX article cites its primary material. 17 sources, in order of first citation. Links open the original publication.
- SonicWall patches exploited SonicOS bug that weakens VPN logins SecurityWeek · 2026-11-07
- U.S. CISA adds SonicWall SonicOS SSLVPN flaw to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-11-07
- CVE-2026-19868 (NVD API record, incl. CISA KEV fields) NIST National Vulnerability Database · 2026-11-07
- CVE-2026-19868 (CVE record JSON, CNA SonicWall and CISA-ADP) CVE Program / MITRE · 2026-11-07
- SonicWall SSLVPN SAML bypass CVE-2026-19868 Ostorlab · 2026-11-07
- CVE-2026-19868: SonicWall SonicOS SSLVPN nFlo · 2026-11-06
- CVE-2026-19868: CWE-308 Use of Single-factor Authentication in SonicWall SonicOS OffSeq Threat Radar · 2026-11-07
- CVE-2026-19868: CISA flags exploited SonicWall SSLVPN SAML and MFA bypass WindowsForum · 2026-11-06
- CWE-308: Use of Single-factor Authentication MITRE CWE · 2026-11
- SonicOS 8 SAML Feature Guide: using SAML SSO for remote access SonicWall · 2026-11
- Gen 7 and newer SonicWall Firewalls – SSLVPN Recent Threat Activity SonicWall · 2025-08-22
- September 2025 update on aggressive ongoing Akira ransomware campaign Arctic Wolf · 2025-09-26
- Frequently asked questions about SonicWall Gen 7 firewall ransomware activity Tenable · 2025-08-07
- Alert AL25-010: SSL VPN vulnerability impacting Gen 7 SonicWall Firewalls (CVE-2024-40766) – Update 1 Canadian Centre for Cyber Security · 2025-08-07
- MySonicWall Cloud Backup File Incident SonicWall · 2025-10-28
- SonicWall security advisory (AV26-872) – Update 1 Canadian Centre for Cyber Security · 2026-09-02
- SonicWall security advisory (AV26-1017) – Update 1 Canadian Centre for Cyber Security · 2026-10-09
Researched and written by the R3KONX analysis desk from the cited primary material. SonicWall's PSIRT advisory page did not render for us, so the fixed build numbers rest on three concordant secondary sources rather than the vendor bulletin itself. Corrections: event@r3konx.asia.
