CISA flags active exploitation of SonicWall SonicOS SSLVPN single-factor authentication flaw
CISA has added CVE-2026-19868, affecting the SSLVPN in SonicWall SonicOS, to its Known Exploited Vulnerabilities catalog based on evidence of real-world attacks. Organisations exposing this VPN to the internet, and US federal agencies in particular, are directly concerned.
What to do now
- Product
- SonicWall SonicOS SSLVPN
- Affected versions
- Versions not specified by the source
- CVE
- CVE-2026-19868
The US Cybersecurity and Infrastructure Security Agency (CISA) added a new entry to its Known Exploited Vulnerabilities (KEV) catalog on 6 November 2026. The flaw, CVE-2026-19868, sits in the SSLVPN component of SonicWall SonicOS and is described as a use of single-factor authentication weakness. CISA listed it because it has evidence attackers are already exploiting it.
The notice is short on detail. It does not name affected SonicOS versions, does not say whether a fix is available, and gives no information on how the flaw is being exploited or by whom. Administrators should check SonicWall's own advisory to establish exposure and the remediation required.
The description suggests that VPN access can rely on a single authentication factor, which makes stolen or guessed credentials more useful to an attacker. Internet-facing VPN gateways are a frequent target because they often lead straight into the internal network.
For US Federal Civilian Executive Branch agencies, the listing triggers requirements under Binding Operational Directive 26-04. The directive tells agencies to prioritise KEV flaws on publicly exposed assets that grant full control after exploitation, and sets expectations for checking whether a system was compromised before it was patched. CISA encourages every organisation to follow the same risk-based approach.
What to do now
- Identify any SonicWall devices with the SonicOS SSLVPN reachable from the internet.
- Review SonicWall's advisory for CVE-2026-19868 and apply the fix or mitigation it specifies.
- As general good practice, enforce multi-factor authentication on all VPN access.
- Review SSLVPN login logs for unusual authentications and check for signs of compromise predating remediation.