DEV Community

Jay
Jay

Posted on

SonicWall CVE-2026-19868: A Valid Password That Skips SAML and Your MFA

SonicWall CVE-2026-19868: A Valid Password That Skips SAML and Your MFA

Bit4Bit DFIR, practical notes for people who actually run the systems.

If your SonicWall firewall sends SSL VPN logins through SAML so your identity provider can enforce multi-factor authentication, patch it now. CVE-2026-19868 lets someone who holds valid credentials for a different login method on the same firewall skip the SAML step, and with it the MFA prompt.

This is not an unauthenticated remote code execution bug. It is narrower than that, and in some ways worse: it defeats the exact control most teams point to when they say remote access is protected by MFA.

What the flaw does

SonicWall's own description, in advisory SNWLID-2026-0014, published November 6, 2026: an authentication enforcement vulnerability in the 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.

In plain terms: the attacker needs a working login for another authentication method on the same appliance, then uses it to get a VPN session without going through SAML at all. The identity provider never sees the login, so its MFA prompt never fires. The flaw only applies when SAML is enabled for SSL VPN logins. If SAML is not in play for your SSL VPN, this CVE is not your problem.

SonicWall rates it CVSS 7.1. CISA's enrichment scores it 7.5. The difference is the privilege assumption: SonicWall's vector assumes the attacker already holds a low-privilege login, CISA's assumes none is required. Either way, the score understates the impact, because the thing being bypassed is MFA itself.

Why it is on CISA KEV, and the date that matters

CISA added CVE-2026-19868 to its Known Exploited Vulnerabilities catalog on November 6, 2026, the same day SonicWall published the advisory. SonicWall says its security team investigated a report of potential exploitation and urges customers to upgrade. The federal remediation deadline in the KEV entry is November 20, 2026, for US federal civilian agencies.

That November 20 date is a federal deadline, not a universal law for every private company. Do not present it as one. What it does tell you is that CISA considers this exploited in the wild, not theoretical, within hours of disclosure. No public proof-of-concept code had been reported at the time of writing, and CISA marks ransomware use as unknown.

Affected and fixed builds

From SonicWall advisory SNWLID-2026-0014, which covers seven vulnerabilities in total. Only CVE-2026-19868 is on CISA KEV from that batch.

  • Gen7: SonicOS 7.3.3-7015 and older are affected. Fixed in 7.3.4-7013 and higher.
  • Gen8: SonicOS 8.2.2-8015 and older are affected. Fixed in 8.2.3-8015 and higher.

SonicWall lists no workaround. The only mitigation is upgrading to the fixed builds, using the supported appliance upgrade path.

What to do

If you run a SonicWall firewall with SAML enabled for SSL VPN logins:

  1. Check your SonicOS build against the table above. If you are on an affected build, upgrade to 7.3.4-7013 or higher on Gen7, or 8.2.3-8015 or higher on Gen8.
  2. While the upgrade is pending, review who holds credentials for alternate authentication methods on that appliance, and whether any of those accounts should exist at all. A second login method you forgot about is the precondition for this bypass.
  3. After patching, review SSL VPN login logs around November 6 and earlier for successful VPN sessions that never touched your identity provider. A login that bypassed SAML will not show up in your IdP logs, which is exactly why it is hard to spot from that side alone.

If you do not use SAML for SSL VPN, this CVE does not apply to you, but the November 6 advisory fixed six other vulnerabilities alongside it, so check whether any of those affect your build.

The DFIR angle

If you investigate a SonicWall environment, do not assume a VPN login without an MFA event means the MFA system failed. Check whether the session came through an alternate authentication method instead. Correlate firewall SSL VPN logs with IdP logs: a successful VPN session with no corresponding IdP authentication is the signature to look for, not just a failed MFA prompt.

And if you find one, the question is not only how the attacker got the alternate credential. It is why that alternate method was enabled on a firewall whose remote access was supposed to be gated by SAML in the first place.


Sources: SonicWall PSIRT advisory SNWLID-2026-0014, published November 6, 2026; CISA Known Exploited Vulnerabilities catalog entry for CVE-2026-19868, added November 6, 2026, federal due date November 20, 2026; SecurityWeek report on the advisory, November 6, 2026. Fixed builds and affected builds are from SonicWall's advisory tables. The November 20 date applies to US federal civilian agencies under CISA's directive, not to all organizations.

Top comments (0)