CVE-2026-19868: SonicWall SSLVPN SAML/MFA bypass joins KEV with a November 20 deadline

A SonicOS SSLVPN flaw lets users with valid credentials bypass SAML and MFA controls. CISA added it to KEV on November 6 with fixes due November 20.
CoeLab Real-World Impact: 89/100 — Urgent. Editorial score v1.0. Evidence checked 2026-11-07T10:10:24.080524+00:00. CVSS and EPSS are separate measures, not this editorial score.
Rating breakdown: exploitation: 30, reachability: 20, consequences: 19, operational relevance: 20.
Who is affected
The vendor record identifies SonicWall SonicOS on Gen7 and Gen8 appliances, with version 7.3.3-7015 and older versions affected on the 7.x branch and version 8.2.2-8015 and older versions affected on the 8.x branch. In practice that is a broad slice of SonicWall's current firewalls, because those build lines are what Gen7 and Gen8 devices run.
The exposed function is the SSLVPN service, the component many organizations treat as their remote-access front door. If that door is reachable from the internet and the deployment uses SAML for VPN authentication, the preconditions for this flaw are present. Organizations using SAML-based identity providers for VPN sign-in should assume the scenario applies to them until they confirm their build levels and configuration.
SonicWall published the issue as advisory SNWLID-2026-0014 on November 6, 2026, as one of several SonicOS vulnerabilities in that advisory. The advisory lists no workaround, so the available responses are patching or removing exposure.
Real-world impact and exploitation evidence
This is an authentication enforcement failure, classified as CWE-308 (use of single-factor authentication). A user holding valid credentials for an alternate authentication method can bypass SAML authentication controls, and successful exploitation can also bypass SAML-enforced MFA. The practical consequence: the additional factor you configured to protect VPN access can be skipped by a credential holder who signs in through the alternate path. This is not a full pre-authentication compromise; the attacker needs some valid credential for an alternate method. But credential reuse, phishing, or purchased credentials are how most real VPN intrusions begin, and MFA bypass is precisely what turns a stolen password into a network foothold.
On exploitation, CISA added CVE-2026-19868 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-06, which is direct evidence of in-the-wild exploitation under KEV's requirements. CISA's coordinated SSVC decision record on NVD likewise marks exploitation as active, automatable: no, technical impact: partial. No public EPSS score exists for this CVE at the time of writing; that absence reflects a newly published record undergoing analysis, not evidence against exploitation.
Timing matters. The CVE record was published 2026-11-06. The KEV addition arrived the same day, which indicates CISA moved fast on an already-exploited issue rather than waiting for analysis. For defenders, the news value is not a theoretical bypass; it is an authentication control on an internet-facing edge device confirmed to fail under active exploitation, with a federal remediation deadline of 2026-11-20 under Binding Operational Directive 26-04.
Attack prerequisites
Published evidence supports a fairly specific prerequisite chain. The attacker needs a user account with valid credentials for an authentication method other than SAML on the SonicOS SSLVPN service. Organizations often configure local accounts, RADIUS, or LDAP alongside SAML, and any such alternate path is the candidate attack surface. The CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C) reflects a network attack with no privileges or user interaction required, but high attack complexity, which is consistent with a credential-dependent bypass rather than a fully unauthenticated exploit.
The published 7.5 score describes moderate network reachability with significant confidentiality impact and changed scope. The KEV listing overrides any inclination to read that as low urgency; a documented MFA bypass on edge authentication that appears in KEV should be treated as urgent regardless of the base score.
What is not documented publicly: the specific protocol or endpoint mechanism by which SAML enforcement is skipped, the number of affected alternate authentication configurations, and whether exploitation leaves distinctive log artifacts. We will not speculate on any of these; readers relying on detection should follow vendor and CISA guidance as it matures.
Actions and fixes
First, inventory. Determine which SonicWall appliances you operate, what SonicOS build each runs, and whether the SSLVPN service is internet-exposed. Devices running 7.3.3-7015 or older, or 8.2.2-8015 or older, are within the vendor's affected range. The vendor's affected-version statement implies fixes ship in builds newer than these two baselines on each branch; before relying on a specific newer build, confirm in the vendor advisory that the build you deploy addresses SNWLID-2026-0014, because our extracted evidence did not include an explicit fixed-version table.
Second, patch promptly. KEV-listed issues carry a November 20, 2026 federal due date under BOD 26-04, and active exploitation means the window between disclosure and abuse is already being used. Patch, reboot per vendor instructions, and verify the running build afterward.
Third, reduce exposure while you work. If the SSLVPN endpoint cannot be patched immediately, restrict it to known networks or a VPN-of-a-VPN arrangement where the architecture allows, and disable or review alternate authentication methods that are not strictly needed. Under BOD 26-04, if mitigations are unavailable, the directive contemplates discontinuing use of the affected product for cloud services; on-prem operators should weigh disabling internet exposure until patched. Finally, review authentication logs for sign-ins that used alternate methods in a pattern inconsistent with your policy, since a MFA bypass leaves behind account-centric traces even when it evades SAML enforcement.
Uncertainty and what could change
NVD's analysis of this record is still in progress (status: Undergoing Analysis), and no EPSS observation exists yet. Both may change in the coming days and could sharpen the picture of exploitation likelihood.
The vendor record lists affected versions as build ceilings and does not, in the evidence we could retrieve, name explicit fixed builds. SonicWall may update SNWLID-2026-0014 with additional resolution details or versions. The same advisory bundles other SonicOS CVEs, and if the vendor adds detail about those or about exploitation behavior, remediation guidance could expand.
CISA notes ransomware-campaign use as unknown and requires no forensic triage per BOD 26-04 for this entry. If ransomware-abuse status changes, or if researchers publish details on how SAML enforcement is skipped, the risk math for organizations running vulnerable builds could shift again; we would expect a KEV-catalog update or a vendor advisory revision in either case.
Sources and evidence date
Evidence for this article was gathered on November 7, 2026, from SonicWall advisory SNWLID-2026-0014 (first published 2026-11-06, last updated 2026-11-06), CISA's KEV catalog entry for CVE-2026-19868 (added 2026-11-06, due 2026-11-20), and NVD's record, which carries the CNA's SonicWall-published data, the CISA SSVC decision (exploitation: active), and NVD status Undergoing Analysis as of 2026-11-07. Distinguish the dates: vulnerability details were published by the vendor and CVE record on 2026-11-06; KEV addition was also 2026-11-06; no separate vendor advisory update and no fixed-version statement was available as of our evidence date.
CoeLab Real-World Impact v1.0 scored this CVE 89 (Urgent) with components: exploitation 30 (KEV), reachability 20 (network vector, changed scope, published AC:H reduces complexity credit), consequences 19 (CVSS 7.5 x2.5), operational relevance 20 (edge-device category heuristic). This is the lab's editorial heuristic, not CVSS, not EPSS, and not a claim about any particular organization's exposure; it weights observed exploitation and attack surface, and readers should treat it as a prioritization signal rather than a measurement.
Primary-source links
https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868
https://nvd.nist.gov/vuln/detail/CVE-2026-19868
https://www.cve.org/CVERecord?id=CVE-2026-19868
AI-assisted research and drafting, with a separate model editorial review. CoeLab ratings are editorial judgments, not a substitute for checking your own versions and vendor advisories. Methodology: https://thecoelab.com/blog/security/methodology
Related Posts
CVE-2026-123890: VMware vCenter authentication bypass exploited since September — CISA patch deadline is November 23
A critical unauthenticated vCenter Directory Service flaw was used in real intrusions weeks before disclosure. CISA gives federal agencies until November 23 — everyone else should not wait longer.
Your USB-C Dock Is Part of Your Network. Test It That Way.
A trending Ethernet investigation shows why docks belong in your network diagram. Here is how to isolate bottlenecks before replacing routers or adapters.
CVE-2026-129448: Apache Roller XML-RPC deserialization gets CISA KEV deadline — unauthenticated remote code execution in versions before 6.1.5
Apache Roller before 6.1.5 runs unauthenticated XML-RPC deserialization before authentication; it is now on CISA's exploited list with a patch deadline of November 23, 2026.