SonicWall SonicOS SSLVPN: SAML and MFA bypass exploited (KEV)
CVE-2026-19868: in the SonicOS SSLVPN service, credentials for an alternate method can bypass SAML and MFA. CISA lists it as exploited.

📌 Later developments: SonicWall SonicOS: the seven flaws in Gen 7 and Gen 8 firewalls (November 6, 2026)
On 6 November 2026 CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities (KEV) catalog. The catalog calls it “SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability”: a vulnerability in the SonicOS SSLVPN service which, by being added to the KEV, is confirmed as exploited in real-world attacks.
For US federal agencies the remediation deadline is 20 November 2026. The CVE record in the NVD database was published on the same day, 6 November, and NVD currently lists it as still undergoing analysis.
This article is based on a single source, the KEV catalog entry with the description published in the NVD database: the information that follows is what is reported there.
What happened
According to the description published in the NVD database, this is an authentication enforcement vulnerability in the SonicOS SSLVPN service. A user holding valid credentials for an alternate authentication method may bypass SAML authentication controls. Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA).
In practice, where VPN access is supposed to go through the SAML identity provider, and therefore through the second factor it requires, the vulnerability may allow a login through another, single-factor authentication method. The name chosen by the KEV catalog and the weakness listed, CWE-308 (Use of Single-factor Authentication), point in the same direction.
The description does not say which alternate authentication methods are involved, or in which configurations.
Technical details
- CVE: CVE-2026-19868.
- Product: SonicWall SonicOS, SSLVPN service.
- Weakness: CWE-308 (Use of Single-factor Authentication).
- CVSS 3.1 score: 7.5 (high), vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N: network attack, high complexity, no privileges required, no user interaction, changed scope, high impact on confidentiality, low on integrity, none on availability. - Exploitation condition: according to the description, valid credentials for an authentication method other than SAML.
- Affected and fixed versions: not reported by the source; they are in SonicWall security advisory SNWLID-2026-0014, referenced by the NVD record.
- Exploitation: confirmed by CISA through its addition to the KEV catalog. Use in ransomware campaigns is, according to CISA, currently unknown.
- Attack chain and indicators: the source does not describe how the vulnerability was exploited and lists no MITRE ATT&CK techniques or indicators of compromise.
In its required action, CISA asks organisations to apply the mitigations provided by the vendor and also refers to its own forensics triage requirements; if mitigations are not available, it asks them to stop using the product.
Impact for European and Italian companies
The SSLVPN service is an entry point into the corporate network from outside, for employees, suppliers and remote support. Many companies have connected their VPN to a SAML identity provider precisely to enforce MFA on every login: a vulnerability that bypasses SAML removes that protection and leaves a password as the only barrier.
For entities in scope of NIS2, timely vulnerability handling and the use of multi-factor authentication are part of the risk-management measures required by Article 21 of the directive. Unauthorised access through the VPN must be assessed for notification to the national CSIRT, which in Italy is CSIRT Italia at ACN. The same applies to healthcare organisations that give staff and suppliers remote access to their systems.
What to do now
- Inventory: identify all SonicWall devices running SonicOS with the SSLVPN service enabled, including those at remote sites or managed by suppliers, and compare their versions with advisory SNWLID-2026-0014.
- Update or mitigate: apply the fixes or mitigations provided by SonicWall. CISA asks organisations to do so or, if they are not available, to stop using the product.
- Reduce exposure: CISA asks organisations to assess how exposed each system is to the Internet. Check from which addresses the SSLVPN service can be reached and whether access can be restricted.
- Review authentication methods: the vulnerability concerns users with credentials for a method other than SAML. Check which methods are enabled on the VPN besides SAML and which accounts can use them; remove accounts that are no longer needed and change any credentials that may have been exposed.
- Check the VPN access logs: look for successful logins that did not go through the SAML identity provider, logins from unusual countries or addresses, and sessions from accounts that do not normally use the VPN. Compare the device logs with those of the identity provider.
- Look for signs of compromise: if you find suspicious logins, follow the forensic triage guidance and check what those sessions reached on the internal network.
How ARXDOME helps
ARX Sentry collects the logs of firewalls and other network devices, enriches them with country, provider and threat lists, and shows them in the SOC pages, where logins, failures and bursts of attempts can be read; the NOC map also flags VPN errors. ARX Shield shows the perimeter, with connections refused by the firewalls and VPN login errors. ARX Expose shows which services your company exposes on the Internet, with recognised products and known vulnerabilities, while ARX Radar detects brute-force attempts under way against your public addresses. With ARX Horizon you can look up vulnerability details from the portal.
Last updated:


