Skip to content
COR Intelligence
Back to The Patch Wave
The Patch WaveAct todayFound by: people

SonicWall firewalls: VPN login flaw can skip SAML and MFA, and it is being used in attacks

COR Solutions9 November 2026
5 min read1,050 words

SonicWall has fixed a SonicOS SSL VPN flaw that can get past SAML sign-in and the MFA it enforces; SonicWall says it investigated a report of possible exploitation, and CISA lists it as exploited. Ask your IT person to update Gen7 firewalls to 7.3.4-7013 or later and Gen8 to 8.2.3-8015 or later.

A compact firewall box with green status lights and two network cables sits on a white cabinet in an empty, sunlit UK open-plan office, with an open laptop glowing on a desk behind.

What happened

SonicWall has fixed a flaw in the SSL VPN on its SonicOS firewalls. Someone who holds a working username and password for another way of signing in can get past SAML sign-in, and with it the multi-factor check that SAML enforces. In SonicWall's words, it "may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls".

SonicWall says it "has investigated a report indicating potential exploitation" and urges customers to upgrade "as soon as possible". CISA went further and added the flaw to its list of exploited flaws on 06/11/2026.

Does this affect you

You are in scope if staff connect to the office through a SonicWall SSL VPN that signs people in with SAML single sign-on. SonicWall says the flaw "ONLY impacts" the SSL VPN "if SAML is enabled for SSLVPN logins". Affected are Gen7 firewalls (TZ, NSa, NSsp, NSv) on SonicOS 7.3.3-7015 or older and Gen8 firewalls (TZ, NSa, NSv) on 8.2.2-8015 or older.

If your SonicWall is a Gen6 or older model, SonicWall says it has reached end of support and gets no firmware updates, so there is no fix coming for it. SonicWall's advice is to move to a Gen8 firewall.

What to do

  1. Ask your IT person: "Do we have a SonicWall firewall, which generation is it, which SonicOS version is it on, and is SAML turned on for the SSL VPN?"
  2. Ask them to back up the firewall's settings first, then update today: Gen7 to 7.3.4-7013 or later (7.3.4-7015 came out on 05/11/2026), Gen8 to 8.2.3-8015 or later. SonicWall says neither update can be rolled back, and that a Gen8 downgrade "can delete all LDAP users and completely reset all multi-factor authentication settings". SonicWall lists no workaround.
  3. Updating does not undo a break-in that has already happened. Ask them to look back through the SSL VPN logins (SonicWall's "Successful SSLVPN User Login" event, ID 1080) for sign-ins they don't recognise, including from before the update.
  4. Ask them to list every account that can still sign in to the SSL VPN another way (local, LDAP, RADIUS or TACACS+ users), remove any that aren't needed and change the passwords on the rest. That is our advice, not SonicWall's: the flaw needs a working password for one of those other methods.
  5. On a Gen6 or older SonicWall, plan the replacement now with your IT person or SonicWall partner, and keep remote access through it to the minimum until then.

Is it being attacked?

CISA says yes: it lists the flaw as exploited from 06/11/2026, with a federal deadline of 20/11/2026. Canada's Cyber Centre says "SonicWall indicates that CVE-2026-19868 is being exploited". SonicWall's own advisory is more careful, saying it investigated "a report indicating potential exploitation". None of them has shared details of the attacks, and we found no security firm's write-up.

Found by

SonicWall's advisory credits Ryan Harris of The Electronic Office. Nothing published says how the flaw was found, so the tag is people.

For developers

  • CVE-2026-19868, CWE-308 (use of single-factor authentication). CNA: SonicWall. Description: "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)."
  • SonicWall SNWLID-2026-0014 (first published and last updated 06/11/2026): "IMPORTANT: SonicWall PSIRT has investigated a report indicating potential exploitation of this vulnerability." and "NOTE: This vulnerability ONLY impacts the SonicOS SSLVPN interface or service if SAML is enabled for SSLVPN logins." Workaround: "None."
  • Affected: Gen7 TZ 270 to 670, NSa 2700 to 6700, NSsp 10700 to 15700, NSv 270, 470 and 870, on 7.3.3-7015 and older; Gen8 TZ 80 to 680, NSa 2800 to 5800, NSv XS, S, M and L, on 8.2.2-8015 and older. Fixed: 7.3.4-7013 and higher; 8.2.3-8015 and higher. The 7.3.4-7015 release notes list it as GEN7-58695.
  • Scores: SonicWall CVSS 3.1 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N); CISA ADP CVSS 3.1 7.5 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N). They differ on privileges required. NVD: undergoing analysis. The advisory's headline 8.8 belongs to two other flaws.
  • The same advisory fixes six more SonicOS flaws, and SonicWall flags possible exploitation for this one only: CVE-2026-107155 and CVE-2026-107154 in the management interface (8.8 each), CVE-2026-82308 a pre-authentication heap overflow in the SSL VPN (7.5), CVE-2026-77708 and CVE-2026-77709 pre-authentication overflows in the TACACS+ client (5.9 each), CVE-2026-19703 weak password hashing on virtual appliances (5.2).
  • KEV (catalogue 2026.11.06): added 06/11/2026, due 20/11/2026, known ransomware use Unknown. CISA SSVC: Exploitation active, Automatable no, Technical Impact partial.
  • The Canadian Cyber Centre's AV26-1133 lists "prior to 8.2.2-8015" without generation labels; SonicWall's advisory and the CVE record put Gen8's fix at 8.2.3-8015, so we follow SonicWall.
  • SonicWall, Gen6: "Gen 6 and older firewalls have reached End-of-Support (EOS), after which SonicWall no longer provides technical support or firmware updates." The advisory itself does not say whether Gen6 is affected.
  • Logs (SonicWall knowledge base, SonicOS 7): Device, Log, Settings, Users category, Group Authentication Access; "Successful SSLVPN User Login" is event ID 1080 and "User Logout" ID 263.
  • UK: no NCSC item. For a live attack the NCSC says to call 0300 123 2040 (24 hours a day); if personal data may have been reached, the ICO says a likely risk must be reported "where feasible within 72 hours".

Sources

Read next

More from The Patch Wave