An attacker with valid credentials for an alternate authentication method may get through SonicWall SonicOS SSLVPN without the SAML controls that normally enforce MFA. CISA listed CVE-2026-19868 for known exploitation on November 6. That makes this an immediate remote-access review for teams running the affected firewalls, especially where a SAML identity provider supplies the second factor.
CISA says: “Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA).” The attacker needs valid credentials for an alternate method. A session that avoids the identity provider can also avoid the MFA event a defender expects to see before VPN access.
Alternate sign-in reaches the VPN
In a SAML-backed deployment, the identity provider handles the MFA step before a user reaches the VPN. SonicWall’s CNA record for this flaw describes an authentication-enforcement weakness in the SSLVPN service: valid credentials for another authentication method may bypass the SAML controls. The record identifies SonicOS Gen7 and Gen8 and lists 7.3.3-7015 and older versions, and 8.2.2-8015 and older versions, as affected.
The identity provider’s MFA policy protects the SAML route; an alternate route to the same VPN session changes which control actually runs. The CNA record describes the conditional capability; CISA’s catalog reports known exploitation of the vulnerability. Scope the first response by affected product and authentication path. For a method-specific detection signature, ask SonicWall for current guidance.
Scope the exposed SSLVPN service
Match the installed SonicOS build on each Gen7 or Gen8 firewall against the affected-version ranges, then identify where SSLVPN is enabled and reachable from outside your network. For each deployment, document whether SAML is used and whether any alternate authentication method accepts valid credentials. Include managed appliances and any firewall still serving remote users after a replacement project.
Pair SSLVPN session records with identity-provider sign-in and MFA events for the same users and period. A VPN session without a corresponding SAML MFA event deserves investigation. Legitimate alternate sign-in can produce the same pattern, so confirm which path the user took before attributing it to exploitation. Preserve the device’s authentication configuration and the session and identity-provider records while you determine which path was used.
Protect remote access now
Use SonicWall’s advisory for SNWLID-2026-0014 to select the mitigation or release for each affected branch; the CNA record names affected versions but does not identify a first-fixed build. Confirm the installed build and the actual SSLVPN authentication configuration after a change. Where your deployment permits it, remove an alternate sign-in path that bypasses the required SAML MFA policy. If vendor mitigation is unavailable, CISA directs operators to discontinue use of the product; arrange alternate remote access.
CISA’s catalog sets November 20 as the federal action due date and points agencies to BOD 26-04 and forensics-triage guidance. Other operators can use the same exposure and authentication-path inventory to prioritize their own response. After making a change, have an authorized test user sign in through the intended route and correlate the VPN session with its SAML MFA event. Investigate any working remote-access path that still lacks the required second-factor check.