Many organizations put SAML single sign-on in front of their SonicWall SSL VPN for one reason: so every remote login goes through the identity provider and its multi-factor prompt. A newly disclosed flaw in SonicOS can break that guarantee. It is already on the U.S. government's list of vulnerabilities known to be exploited.

On November 6, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-19868 to its Known Exploited Vulnerabilities (KEV) catalog. The entry is titled "SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability" and has a remediation due date of November 20. CISA's SSVC assessment in the National Vulnerability Database lists exploitation as "active."

The facts below come from the official CVE record, NVD and the KEV entry. SonicWall's own advisory, SNWLID-2026-0014, is referenced in those records, but we did not review the vendor's own text.

What the bug does

According to the CVE record, which SonicWall filed as the CVE Numbering Authority, "an authentication enforcement vulnerability in SonicOS SSLVPN service 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)."

Here is what that means in practice. A SonicWall firewall can authenticate SSLVPN users in more than one way. SAML hands the login to an external identity provider, which usually also enforces MFA. A firewall can also hold other sources of credentials. If an administrator has set SAML as the required path, users should not be able to get around it. This bug lets someone who has a working username and password for one of the other methods get past the SAML requirement. If the identity provider was the only place MFA was enforced, that protection may be skipped too.

CISA classifies the weakness as CWE-308, "Use of Single-factor Authentication." In plain terms, a login that should have needed two factors may end up needing one.

Note the main precondition: the attacker needs valid credentials. This is not a way to break in with no credentials at all. But stolen, phished, reused and leaked VPN passwords are plentiful, and MFA exists precisely to make a stolen password useless on its own. A flaw that makes the password enough again is why this one matters.

Which devices are affected

The CVE record and NVD list two product lines:

  • SonicOS Gen7: version 7.3.3-7015 and older
  • SonicOS Gen8: version 8.2.2-8015 and older

Neither the CVE record, NVD nor the KEV entry names the fixed firmware builds. Defenders should get those from SonicWall advisory SNWLID-2026-0014 or through SonicWall support.

How serious is it?

NVD shows a secondary CVSS 3.1 score of 7.5 (High) with the vector AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N. Decoded, that means:

  • The flaw can be reached over the network (AV:N), with no prior privileges on the device (PR:N) and no user interaction (UI:N).
  • Attack complexity is rated high (AC:H). The sources do not say why; the need for valid alternate-method credentials and a particular configuration may be factors.
  • Scope is "changed" (S:C), which in CVSS terms means the impact can extend beyond the vulnerable component.
  • Confidentiality impact is high, integrity impact is low, and there is no availability impact.

CISA's SSVC data adds context: exploitation "active," automatable "no," technical impact "partial." "Active" means CISA's assessment is that exploitation is occurring. "Automatable: no" suggests the attack is harder to run at scale than a fully automated one. For a perimeter VPN, the "active" rating is the one to pay attention to.

The KEV entry lists known ransomware campaign use as "Unknown." None of the sources name an attacker or campaign, and we are not attributing one.

Timeline

  • August 14, 2026: CVE ID reserved by SonicWall.
  • November 6, 2026, 18:55 UTC: public date in the CVE record; the record was published at 19:03 UTC. The CVE record marks the discovery source as "EXTERNAL," meaning the bug was reported from outside the company.
  • November 6, 2026: CISA adds the flaw to KEV the same day. NVD marks it "Undergoing Analysis."
  • November 20, 2026: KEV remediation due date.

CISA added the flaw to KEV on the same day the CVE record was published. That suggests CISA already had evidence of exploitation when the advisory came out, though the sources do not say so directly. Either way, defenders have very little time between learning about the bug and needing to act.

What It Means for Defenders

Who is affected: anyone running SonicWall Gen7 firewalls on SonicOS 7.3.3-7015 or older, or Gen8 firewalls on 8.2.2-8015 or older, with SSLVPN enabled. The highest risk is for organizations that rely on SAML to enforce MFA for VPN users while other authentication methods are still configured on the device.

Patch or mitigate first. CISA's required action is to apply mitigations per vendor instructions, in line with BOD 26-04, or to discontinue use of the product if mitigations are not available. The November 20 deadline is binding on agencies covered by that directive. Everyone else should treat it as the latest reasonable date, not a target. The sources we read do not list fixed builds, so check SNWLID-2026-0014 for the exact firmware versions and any interim workarounds SonicWall recommends.

Check your authentication setup. Make a list of every authentication method the firewall accepts for SSLVPN: local users, directory-backed accounts and anything else besides SAML. Every one of those is a potential way around SAML until you patch. Accounts that exist only for convenience or legacy reasons are worth removing anyway.

Rotate credentials. The attack needs a valid alternate-method credential, so rotate passwords for local and non-SAML VPN accounts, starting with any account that could have been reused, phished or exposed. Pay particular attention to service and admin accounts.

Look back through your logs. Because exploitation is rated active, review SSLVPN login records for sessions that succeeded without a matching SAML or identity-provider event. Also look for unexpected use of local or legacy accounts, and for logins from unusual locations since well before November 6. Any VPN session that cannot be tied to an MFA event should be investigated as a possible intrusion, not just closed.

For CMMC and federal contractors: MFA for remote network access is a core control. If a firewall accepted single-factor logins, document what you found, what you changed and when. If the review turns up unexplained sessions, your incident-reporting obligations may apply.

We will update this story once SonicWall's advisory text or independent reporting adds detail on fixed versions or exploitation activity.

Sources