On this page (7 sections)
CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog on November 6, 2026. The flaw is in the SonicOS SSLVPN service: a user who holds valid credentials for an alternate authentication method may be able to bypass SAML authentication controls, including multi-factor authentication (MFA) enforced through SAML.
If your organization or a client uses a SonicWall firewall for remote access VPN with SAML single sign-on, this is worth checking today. Public detail is thin so far, and this article separates what is confirmed from what is still unknown.
What happened
The GitHub advisory entry, which reproduces the NVD record, describes an authentication enforcement problem in the SonicOS SSLVPN service. A person with valid credentials for a different authentication method may be able to skip the SAML controls. Successful exploitation may also bypass MFA that SAML is meant to enforce.
The CISA KEV entry marks the flaw as exploited and sets a remediation due date of 2026-11-20 for US federal agencies. CISA lists known ransomware campaign use as Unknown. The vendor advisory is SNWLID-2026-0014.
Why this weakness matters
SAML single sign-on lets your identity provider decide who may log in, and it is usually where MFA is enforced. The weakness class here, CWE-308, means a login path that should require more than a password can be satisfied with fewer factors.
The practical reading of the description is that the VPN may accept more than one way to authenticate. If an alternate method (for example a local or directory account) is still enabled alongside SAML, valid credentials for that method might be enough to get in without the SAML step or its MFA prompt. That is our interpretation of the short description, not a confirmed attack path. The CVSS metrics list high attack complexity and no privileges required, with high confidentiality impact.
A VPN session usually lands inside your internal network, so a bypass here is more serious than a single compromised web account. The attacker still needs valid credentials for some method, so stolen or reused passwords become more valuable.
Who is exposed
- Organizations running SonicOS with the SSLVPN service enabled.
- Setups that use SAML authentication for VPN users, particularly where SAML is the only place MFA is enforced.
- Setups where more than one authentication method is configured for the same VPN users or portal.
- Managed service providers and agencies who administer SonicWall devices for clients.
If SSLVPN is not enabled on your device, this specific service is not in play, but confirm that rather than assume it.
How to check your exposure
- Inventory every SonicWall device and note whether SSLVPN is enabled and reachable from the internet.
- In the device's authentication settings, list which methods are configured for SSLVPN users (SAML, local users, LDAP/RADIUS or others).
- Open the SonicWall advisory SNWLID-2026-0014 and compare your SonicOS version and model against its affected and fixed lists.
- Review SSLVPN login logs for the period before today for successful logins that did not pass through your identity provider, or that came from unexpected addresses or countries.
- Compare VPN logins with your identity provider's sign-in logs. A VPN session with no matching SAML sign-in and MFA event deserves investigation.
What to do now
CISA's required action says to apply mitigations in line with vendor instructions, and to discontinue use of the product if mitigations are not available. Start from the vendor advisory, since it is the authoritative source for fixed versions and workarounds.
- Read SonicWall advisory SNWLID-2026-0014 and apply the listed fix or mitigation.
- If a patched SonicOS release exists for your model, schedule the upgrade as urgent and take a configuration backup first.
- Until patched, consider disabling alternate authentication methods for SSLVPN so SAML is the only path, if the advisory and your setup allow it.
- If SSLVPN is not needed, disable it or restrict access to known source addresses.
- Reset passwords for VPN-capable accounts, especially any that were used with an alternate method, and revoke active VPN sessions.
- Review recent VPN logins as described above and treat unexplained ones as a possible incident.
- Check what a VPN user can reach internally and tighten segmentation where access is broad.
- Record the device versions and the date of mitigation for your audit trail.
If you find signs of unauthorized access, follow an incident process: isolate affected accounts, rotate credentials and secrets reachable from the VPN, and see our guide on what to do when a website is hacked for the general approach.
Detection and monitoring afterwards
- Alert on VPN logins that have no matching identity provider sign-in event.
- Alert on logins from new countries, new hosts or unusual hours for each account.
- Watch for administrative changes on the firewall, such as new local users or changed authentication settings.
- Keep an eye on the CISA KEV entry and the SonicWall advisory for updates, since details and fixed versions may change.
Remote access is only one part of your exposure. Your public sites and services still need regular checks. A read-only security scan of the web properties you run helps you keep an inventory of what is exposed, and monitoring for certificate, DNS and header changes can flag unexpected changes on the public side while you work through the VPN review.
Timeline
| Date | Event |
|---|---|
| 2026-11-06 | CVE-2026-19868 published in NVD and the GitHub Advisory Database |
| 2026-11-06 | Added to the CISA KEV catalog |
| 2026-11-20 | CISA remediation due date for covered federal agencies |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
