DevSecOps

SonicWall SonicOS SSL-VPN flaw exploited to bypass SAML auth and MFA (CVE-2026-19868, KEV)

SonicWall SonicOS SSL-VPN contains a use-of-single-factor-authentication vulnerability that lets a user with valid credentials for an alternate authentication method bypass SAML authentication controls — including SAML-enforced MFA. The NVD record carries CVSS 7.5 (HIGH, a secondary score), and CISA added it to its KEV catalog on November 6, 2026: active exploitation confirmed.

The official CVE data

Per the official NVD record (verified by Argos against the NIST API on 2026-11-12):

- **CVE-2026-19868** · published 2026-11-06 · severity **HIGH** · CVSS 3.1: **7.5** - Vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N` — network vector, no user interaction, and **changed scope**: the flaw lets an attacker cross from the VPN into other components/trust boundaries, with high confidentiality impact. - **CISA KEV addition:** 2026-11-06 (product: SonicWall SonicOS SSLVPN), with active exploitation confirmed.

The core problem: MFA you can route around

The mechanics are what make this worrying: there's no need to steal the MFA or break SAML — having valid credentials for an alternate authentication method enabled on the appliance is enough to get in while bypassing SAML controls. Perimeter firewalls and VPNs remain the favorite vector against enterprises, and the SonicWall ecosystem carries a repeated history of perimeter incidents (2021, 2022, 2024), which turns every new SonicOS CVE into a natural candidate for fast exploitation.

What to do

1. Apply the vendor's fix on SonicOS appliances with exposed SSL-VPN as a matter of urgency. 2. Audit enabled alternate authentication methods: any path that doesn't go through SAML+MFA is a potential bypass. 3. Review VPN authentication logs for sessions that entered via non-SAML methods since the flaw was published. 4. Where possible, pull the SSL-VPN off the internet and keep it behind a management VPN or allow-IP lists.

Closing

MFA is not a wall if an alternate path routes around it: that's the general lesson of CVE-2026-19868, and it applies to any corporate VPN. If your perimeter includes SonicWall, this week is for patching, auditing methods and reading logs — in that order.

--- **Primary source:** NVD (NIST) — official record for CVE-2026-19868. https://nvd.nist.gov/vuln/detail/CVE-2026-19868 · published 2026-11-06 · HTTP 200 verified 2026-11-12; CVSS obtained from the official services.nvd.nist.gov API on 2026-11-12 (Argos). **Additional source:** CISA KEV catalog (official JSON feed, downloaded 2026-11-12) — CVE added 2026-11-06. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json **Category:** Cybersecurity · **Topics:** SonicWall, SonicOS, SSL-VPN, SAML, MFA, CISA KEV, CVE-2026-19868. **Verification status:** CVSS, vector and dates re-verified on 2026-11-12 against official sources (NVD API + CISA KEV catalog) during the edit pass (loop 3); the ecosystem's incident history is editorial context from the Argos batch. Action recommendations are HOLOS editorial analysis.