NVD published CVE-2026-19868 on November 6, 2026, and CISA added it to the KEV catalog the same day, with a deadline of November 20. Disclosure and confirmed exploitation landed together: there was no grace period.
This flaw doesn't hand out code execution. For a VPN, it does something arguably worse: it makes the authentication control you chose to enforce optional. A user holding valid credentials for an alternate authentication method can get past the SAML configured on the SSLVPN — and therefore past the MFA that SAML enforces.
It's the second SonicWall KEV story this fall, after the SMA1000 appliances in September.
The Vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-19868 |
| Product | SonicWall SonicOS, SSLVPN service |
| CVSS 3.1 (CNA) | 7.5 (HIGH) — AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N |
| NVD CVSS | not yet published (status Undergoing Analysis) |
| Type | Use of single-factor authentication (CWE-308) |
| NVD publication | 2026-11-06 |
| Added to CISA KEV | 2026-11-06 |
| CISA deadline | 2026-11-20 |
| Known ransomware use | unknown (CISA field: "Unknown") |
| Vendor advisory | SNWLID-2026-0014 |
NVD description:
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).
The 7.5 comes from the CNA and is recorded by NVD as a secondary source. NVD hasn't published its own assessment yet.
Why It Matters
Plenty of organizations wired their SonicWall SSLVPN to a SAML identity provider — Entra ID, Okta, an in-house IdP — for one reason: to enforce MFA on remote access. The assumption is simple: a stolen password alone won't get an attacker past the second factor.
CVE-2026-19868 breaks that assumption. Per the description, someone with valid credentials for an alternate authentication method can get in without going through SAML, so the MFA that SAML carries never applies.
Reading the vector:
PR:N: the CNA considers that no privileges on the firewall are needed. The credentials involved belong to a user, not an administrator.AC:H: a specific precondition is required. The description tells you which one: credentials for another authentication method.S:CandC:H: the impact reaches beyond the vulnerable component — which is exactly what a VPN is for. What the attacker gets is a foothold on the network behind it.
Our inference, not a confirmed fact: the most likely scenario involves credentials from a leak, an infostealer or a forgotten local account — credentials that MFA had made useless. This flaw makes them usable again. Neither NVD nor CISA describes the exploitation campaign.
Affected Versions
NVD hasn't published a CPE configuration for this CVE yet, so its data contains no version range. Affected and fixed versions are listed in SonicWall advisory SNWLID-2026-0014, referenced by both NVD and CISA. That's the document to follow when deciding which build to install on each model.
Detection
- Successful SSLVPN logins with no matching IdP event: correlate the firewall's VPN logs with your SAML IdP's sign-in logs. A VPN session with no corresponding SAML authentication in the same time window is the key signal.
- Local or LDAP accounts logging into the VPN when policy says everyone goes through SAML
- Unusual source IPs, especially hosting providers and commercial VPN exits
- Post-login activity: share access, RDP, LDAP queries originating from the SSLVPN address pool
Mitigation
1. Apply the fix from SNWLID-2026-0014
The CISA deadline is November 20. The KEV entry also points to directive BOD 26-04 and its forensic triage requirements: patching isn't enough if the appliance has already been exposed.
2. Remove alternate authentication methods you don't need
The flaw relies on another method existing. Inventory what's still allowed on the SSLVPN — local accounts, LDAP, RADIUS — and disable whatever isn't in use. A break-glass local account shouldn't be able to open a VPN session.
3. Rotate exposed credentials
Reset passwords for every account that has an alternate method, starting with those whose only real protection was "MFA will catch it anyway".
4. If you find a suspicious session
- Kill active VPN sessions and disable the accounts involved
- Hunt for lateral movement from the SSLVPN address pool
- Assume the VPN gave the attacker a position on the internal network and handle it as an incident
Why Continuous Monitoring of Your SonicWall Fleet Matters
Published and added to KEV on the same day, with a 7.5 that won't put it at the top of anyone's priority list: that's exactly the kind of flaw that slips between two vulnerability reviews. Meeting a two-week deadline means knowing right away which firewalls expose an SSLVPN, and on which version.
With cveo.tech, track your SonicWall firewalls with their SonicOS version and get alerted as soon as a CVE affecting them lands in the CISA KEV catalog.