CVERadar
HIGH · CVSS 3.1 7.5CISA KEV · added 2026-11-06EPSS n/aThreat level 53

CVE-2026-19868: SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability

SonicWall · SonicOS SSLVPN · NVD published 2026-11-07 · posted 2026-11-06 · last modified 2026-11-07

CVE-2026-19868 at a glance

CVE-2026-19868 is a high-severity vulnerability in SonicWall SonicOS SSLVPN, with a CVSS 3.1 base score of 7.5. NVD published it on 2026-11-07 and classifies the weakness as CWE-308. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-06; the federal remediation due date is 2026-11-20. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 53/100.

What it is

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).

WeaknessCWE-308 definition
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N (source: CVE Numbering Authority)
CISA due date2026-11-20 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

CVERadar report: CVE-2026-19868: SonicWall SonicOS SSLVPN flaw exploited in the wild, what we know

What this means for a small business

CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog on 2026-11-06. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs SonicWall SonicOS SSLVPN, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-20 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Install the latest update from SonicWall. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
  • If you cannot patch yet. Follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  • Check your exposure. Find out whether SonicWall SonicOS SSLVPN can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
  • When to call IT support. Call your IT support provider now if you run SonicWall SonicOS SSLVPN and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

If nobody on staff owns the firewall, LayerLogix firewall management covers configuration, monitoring and policy reviews.

Built from the CISA KEV entry and the NVD record for CVE-2026-19868; nothing here goes beyond those sources.

Exploitation evidence

First exploit evidence seen: 2026-11-06 (earliest date across the sources below).

Exploited in the wild

Sources: CISA KEV.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. (source: CISA KEV)

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources