Becky Simms Avatar

Written by Becky Simms

Contributor

SHARE
A corporate firewall guarding remote VPN connections, with a shield over encrypted data streams between a laptop and a server

A firewall flaw that lets an attacker walk around multi-factor authentication is now confirmed as exploited in the wild, and the clock is running. The US Cybersecurity and Infrastructure Security Agency (CISA) added the SonicWall SonicOS vulnerability CVE-2026-19868 to its Known Exploited Vulnerabilities (KEV) catalog on 6 November 2026, and US federal civilian agencies have until 20 November 2026 to patch. For everyone else running SonicWall, the same evidence applies: this is not a theoretical weakness, it is one attackers are already using.

The flaw sits in the SSL-VPN service of SonicWall firewalls, the remote access route that lets staff connect into a company network from outside. When an organisation routes those VPN logins through SAML single sign-on, the identity provider is supposed to enforce multi-factor authentication. CVE-2026-19868 breaks that chain. A user holding valid credentials for a different login method on the same firewall can bypass the SAML controls, and with them the MFA prompt that SAML was supposed to enforce.

What the Flaw Actually Does

SonicWall describes it plainly in advisory SNWLID-2026-0014, published 6 November 2026: “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).” The weakness is classified as CWE-308, use of single-factor authentication.

Put simply, the firewall asks for a second factor at the front door, and this flaw lets an attacker walk around the side and skip it entirely. It matters because it does not defeat MFA by cracking it. It avoids the step where MFA happens at all. The SAML flow is the part of the login that enforces the second factor, so bypassing SAML means the second factor never gets a chance to run.

Two limits keep the scope narrower than the headlines suggest, and both matter. First, the flaw only affects SSL-VPN services where SAML authentication is enabled for SSL-VPN logins. If your VPN does not use SAML, this CVE does not apply to you. Second, exploitation needs valid credentials for an alternate authentication method, such as a local account or another configured directory service. This is not an unauthenticated login with no password. It is a bypass that turns one valid credential into a way past the MFA check that was supposed to stand behind it.

The flaw was discovered and reported by Ryan Harris of IT services provider The Electronic Office, a credit confirmed by Help Net Security, SecurityWeek and CyberPress.

Who Is Affected and Which Builds Fix It

The affected firmware is SonicOS 7.3.3-7015 and older on Gen7 firewalls, and SonicOS 8.2.2-8015 and older on Gen8 firewalls. That covers Gen7 and Gen8 TZ, NSa and NSsp hardware firewalls and NSv virtual appliances, according to the advisory and SecurityWeek coverage.

Firewall generationAffected versionsFixed version
Gen7 (TZ, NSa, NSsp, NSv)SonicOS 7.3.3-7015 and older7.3.4-7013 or higher
Gen8 (TZ, NSa, NSv)SonicOS 8.2.2-8015 and older8.2.3-8015 or higher

SonicWall rates the flaw CVSS 7.1, high severity. The National Vulnerability Database and CISA’s enrichment score it 7.5, also high. The difference comes from the scoring assumptions: SonicWall’s vector assumes the attacker already holds a low-privilege login, while the NVD record scores it with no privileges required. Either way, the severity label is the same, and the KEV listing is what should drive the urgency, not the decimal.

Why CISA Put It on the Exploited List

CISA’s KEV catalog only lists vulnerabilities with evidence of real-world exploitation, so the 6 November listing is itself the confirmation that this flaw has been used in attacks. SonicWall’s own wording is more cautious: its security team “investigated a report indicating potential exploitation of this vulnerability” and urged customers to upgrade to the latest version as soon as possible. Canada’s cyber security centre issued its own alert on 6 November warning of exploitation and urging organisations to update.

Under Binding Operational Directive 26-04, US federal civilian agencies must apply the vendor fix by 20 November 2026. CISA lists known ransomware use for this CVE as unknown. No public proof-of-concept code had been reported at the time of writing, and the estimated probability of exploitation in the next 30 days, the EPSS score, stands at 0.62 percent, low in absolute terms but beside the point once exploitation is already confirmed.

For private organisations the 20 November date is not a legal deadline, but it is a useful one. It is the date by which the US government expects its own agencies to be patched, and the exploitation evidence behind it applies to any organisation running the same firmware.

What to Do Right Now

If you run a SonicWall firewall, work through these steps in order.

1. Check whether you are affected. Look at the SonicOS version on each firewall and check whether SAML is enabled for SSL-VPN logins. If SAML is not enabled for SSL-VPN, this CVE does not apply to that device. If it is, and the firmware is 7.3.3-7015 or older on Gen7, or 8.2.2-8015 or older on Gen8, you are affected.

2. Patch to the fixed build. Upgrade Gen7 firewalls to SonicOS 7.3.4-7013 or higher, and Gen8 firewalls to 8.2.3-8015 or higher, following the supported appliance upgrade path. Do this before 20 November, and treat it as urgent rather than routine.

3. If you cannot patch immediately, remove the alternate route. SonicWall’s advisory lists a mitigation for organisations that cannot upgrade straight away: disable or delete any active LDAP, RADIUS and TACACS+ authentication servers configured on the firewall, so there is no alternate login method for the bypass to use. The settings sit under Device, Users, Settings, Authentication, then Configure RADIUS, Configure LDAP or Configure TACACS+, depending on the service. Several outlets have reported that no workaround exists, but the advisory itself publishes these steps, and they are worth using while a patch window is arranged.

4. Review who can log in. Audit local and alternate-method accounts on the firewall, remove stale or shared credentials, and check SSL-VPN login logs for successful logins that skipped the SAML flow. SonicWall has published no indicators of compromise, so look for the pattern rather than a known signature: VPN logins that succeeded without a corresponding SAML or MFA event in your identity provider.

5. Do not judge the update by this CVE alone. The same advisory fixes six other flaws, listed below, including two rated 8.8. Patching closes all seven at once.

The Same Advisory Fixes Six More Flaws

SNWLID-2026-0014 covers seven CVEs in total, and CVE-2026-19868 is not the highest scored of them. The other six are:

CVESeverityWhat it is
CVE-2026-1071558.8Permissive cross-domain policy in the SonicOS management interface, which could let a remote unauthenticated attacker perform unauthorised operations in specific conditions
CVE-2026-1071548.8Session validation flaw in the SonicOS management interface, with the same potential for unauthorised operations
CVE-2026-823087.5Pre-authentication heap buffer overflow in the SSL-VPN service, which could let a remote unauthenticated attacker cause an application level denial of service
CVE-2026-777085.9Pre-authentication stack buffer overflow in the TACACS+ authentication client, denial of service
CVE-2026-777095.9Pre-authentication heap buffer overflow in the TACACS+ authentication client, denial of service
CVE-2026-197035.2Weak password hashing on SonicOS virtual appliances, which could let an attacker with existing local access disclose a platform credential

The two 8.8 flaws need a user to click something or a specific session condition to be exploitable, which is why they did not make the KEV list. They are still worth patching, and the same firmware update closes them.

The advisory also arrives days after SonicWall detailed two unpatched vulnerabilities in its end-of-life Global Management System, CVE-2026-109593 and CVE-2026-109594, and urged customers to upgrade to Network Security Manager, as The Hacker News reported. If you still run GMS, that is a separate migration to plan.

What Is Still Unknown

Honesty about the gaps matters as much as the facts. Neither SonicWall nor CISA has said who is behind the attacks, how many organisations have been hit, or what the attackers did once they got in. No indicators of compromise have been published, and no security company has yet published an analysis of the attacks, according to Help Net Security. The advisory does not confirm a campaign, only that a report of potential exploitation was investigated.

That uncertainty is normal in the first days after a KEV listing, and it is not a reason to wait. KEV admission requires evidence of active exploitation, and the patch already exists. The sensible reading is that the risk is confirmed, the fix is available, and the remaining unknowns are about the attackers, not about what to do.

The Lesson Beyond This Patch

This flaw is a reminder that turning MFA on is not the same as enforcing it on every route into the network. Many organisations enabled SAML and MFA for their VPN and reasonably believed the second factor protected every login. CVE-2026-19868 shows a second path into the same service that never asked for it. The fix is a firmware update, but the lasting lesson is an audit habit: after any authentication change, check every login method a service accepts, not just the one you configured, and make sure the MFA requirement applies to all of them.

This article is for general information only and is not security advice. Figures come from the sources linked in the article, cross-checked against independent coverage. No attacker attribution, victim count or indicators of compromise have been published for CVE-2026-19868.

Frequently Asked Questions

What is CVE-2026-19868?

CVE-2026-19868 is an authentication enforcement flaw in the SonicOS SSL-VPN service. A user with valid credentials for an alternate authentication method can bypass SAML authentication controls, and with them the multi-factor authentication that SAML enforces. It is classified as CWE-308, use of single-factor authentication, and scored 7.1 by SonicWall and 7.5 by the National Vulnerability Database.

Which SonicWall firewalls are affected?

Gen7 firewalls running SonicOS 7.3.3-7015 and older, and Gen8 firewalls running SonicOS 8.2.2-8015 and older, are affected, but only where SAML is enabled for SSL-VPN logins. The fixed builds are SonicOS 7.3.4-7013 for Gen7 and 8.2.3-8015 for Gen8.

Is CVE-2026-19868 actually being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 6 November 2026, a list that only includes flaws with evidence of real-world exploitation. SonicWall says it investigated a report indicating potential exploitation. No attacker has been named and no victim count has been published.

What is the patch deadline?

US federal civilian agencies must remediate by 20 November 2026 under Binding Operational Directive 26-04. Private organisations face no legal deadline, but the same exploitation evidence applies to their firewalls, so 20 November is a sensible target.

Is there a workaround if I cannot patch yet?

SonicWall’s advisory lists one mitigation: if SAML is in use and upgrading is not possible, disable or delete any active LDAP, RADIUS and TACACS+ authentication servers configured on the firewall. Several outlets have reported that no workaround exists, but the advisory itself publishes these steps.

Who discovered the flaw?

Ryan Harris of IT services provider The Electronic Office discovered and reported CVE-2026-19868 to SonicWall.


About the Author

Becky Simms

Becky Simms

Becky Simms is a technology writer with 9+ years in consumer electronics, streaming services, and device troubleshooting. Becky verifies tech news and outages against official status pages and verified outage reports, covering service outages, AI products, tech companies, and new technology coverage, and separates what is confirmed from what is still unproven. Becky’s guides show readers how to check a service themselves, right now, instead of relying on rumours.