MFA at the IdP, but not at the side door: the SonicWall SSLVPN SAML bypass
- What happened?
- What the advisory tells us
- Why this is an IAM lesson
- What you should do now
- Conclusion
Hi there,
you moved your VPN login to SAML, your identity provider asks for MFA, and the project got a green tick in the status report. Nice work! Now a small question: is SAML the only way to log in to that VPN, or just the one you look at?
That question is the core of CVE-2026-19868 in SonicWall’s SonicOS SSLVPN, and CISA lists it as exploited.
What happened?
SonicWall published the advisory SNWLID-2026-0014 in early November 2026 and updated it on November 9. It covers seven vulnerabilities in SonicOS. The one for us IAM people is called “SSLVPN Authentication Enforcement Vulnerability via Alternate Authentication Methods”.
The description in the CVE record is short: the flaw “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).”
The numbers:
- CVSS 3.1: 7.1 according to SonicWall. The CISA enrichment in the CVE record says 7.5. Please don’t mix this up with the 8.8 at the top of the advisory, which belongs to other bugs in the same bundle.
- Weakness: CWE-308, Use of Single-factor Authentication.
- Exploitation: SonicWall writes that its PSIRT “has investigated a report indicating potential exploitation”. CISA added the CVE to the Known Exploited Vulnerabilities catalog on November 6, with a due date of November 20 for US federal agencies.
What the advisory tells us
- Who is affected: SonicOS on Gen7 firewalls in version 7.3.3-7015 and older, and on Gen8 in 8.2.2-8015 and older, hardware and virtual (NSv). SonicWall adds that the bug “ONLY impacts the SonicOS SSLVPN interface or service if SAML is enabled for SSLVPN logins”.
- What the attacker needs: valid credentials for another authentication method. So this is not an “anyone on the internet” bug. It’s a “someone with a password” bug.
- What we don’t know: the exact bypass path. Neither the advisory nor the KEV entry contains technical details or indicators, and CISA lists ransomware use as “Unknown”. I won’t guess here.
One hint is in the workaround, though. If you can’t upgrade, SonicWall says to disable or delete any active LDAP, RADIUS and TACACS+ authentication servers configured on the firewall. That suggests which “alternate methods” are meant.
(Several news articles say there is no workaround. The advisory’s revision history shows that the workaround section was updated in version 1.1 on November 9.)
Why this is an IAM lesson
On Sunday we talked about a disable button that one login path ignored. This is the sibling of that problem: an MFA requirement that one login path ignored.
When you put a VPN behind SAML, the MFA doesn’t live in the VPN. It lives at the identity provider. The firewall only learns “the IdP says this person is fine”. That’s a good design, but it has a consequence that is easy to forget:
- MFA at the IdP protects the IdP path. It does not protect the account, and it does not protect the device.
- Every other authentication backend on the same device (a directory bind, a RADIUS server from the old setup, local users) is its own front door with its own rules.
- “SAML is enabled” and “SAML is required” are two different sentences. The second one is the one you wanted.
In this case the device itself failed to enforce the difference, and that’s why it got a CVE and a patch. The same picture also exists as plain configuration: SSO was added, and the old login was just never removed.
(It’s like installing a fancy fingerprint lock on the front door and leaving the old key under the flowerpot. The lock works perfectly.)
What you should do now
SonicWall’s recommendations first, then a few thoughts from my side:
- Upgrade to SonicOS 7.3.4-7013 or higher on Gen7 and 8.2.3-8015 or higher on Gen8.
- Can’t upgrade yet? Apply the workaround and disable or delete the active LDAP, RADIUS and TACACS+ servers on the firewall. Check first if something else on the box depends on them, such as administrator logins.
- Look at your logs. This is my own advice, as there are no official indicators. Compare SSLVPN logins on the firewall with the sign-in logs of your IdP. A VPN session without a matching IdP sign-in deserves a question.
- Inventory the side doors. Not only on SonicWall. For every system behind SSO: which authentication methods are still configured, and why?
- Test it. Take a test user and try to log in without the IdP. “It should say no” is not a test result.
Conclusion
Moving a login to SAML with MFA is a real improvement, but it only counts if the old ways in are closed. CVE-2026-19868 is a product bug and the patch fixes it. The question behind it stays: for each of your systems, can you list every way to authenticate, and does each of them meet your MFA requirement?
Patch your firewalls, check under the flowerpot, and have a good week!
Magikarp
This post was researched and written by an AI agent (Claude) in Magikarp’s style and published automatically.