On 6 November 2026, CISA added a SonicWall flaw, CVE-2026-19868, to its Known Exploited Vulnerabilities (KEV) catalog. That listing means there is evidence attackers are already using it. The flaw sits in the SSL VPN of SonicOS and lets someone who holds valid credentials for an alternate login method skip the SAML check, including the multi-factor step that was supposed to protect the session.

Our view is simple. The useful question is not whether your MFA is strong. It is whether anyone in your organisation knows which firewall version you run, and who is responsible for updating it. For many shops, branch offices and small businesses, the honest answer is "the vendor who installed it, some time ago".

How the bypass works

NVD describes CVE-2026-19868 as an authentication enforcement flaw in the SonicOS SSL VPN service. The service accepts more than one way to log in. SAML with MFA is the path most administrators have in mind when they say "our VPN is protected by MFA". But when another login method is enabled on the same service, valid credentials for that method can be enough to get through without the SAML verification. The second factor is never requested, because the login never passes through the door where it is requested.

Diagram of two login paths into the same SonicOS SSL VPN: the official SAML login with MFA, and an alternate login method that skips the SAML and MFA checks

This does not mean MFA as a technology is broken. The gate is intact; the problem is the side door. The attacker still needs valid credentials for that other method, but credentials are exactly what phishing, reuse and earlier data leaks supply.

What is confirmed, and what to double-check

Per the NVD record and CISA's alert, the following is confirmed:

  • The flaw was published on 6 November 2026 and CISA added it to the KEV catalog the same day, based on evidence of active exploitation.
  • Affected versions are SonicOS Gen7 7.3.3-7015 and older, and Gen8 8.2.2-8015 and older. NVD lists a CVSS 3.1 score of 7.5 (High).
  • CISA set 20 November 2026 as the deadline for US federal civilian agencies under BOD 26-04, and encourages all organisations, not only federal ones, to prioritise KEV entries. For agencies that patch late, it asks them to check for prior compromise.

TechBytes reports two further points: the fixed versions are 7.3.4-7013 for Gen7 and 8.2.3-8015 for Gen8, and SonicWall states there is no configuration workaround. Treat those as reported rather than confirmed until you have read SonicWall's own advisory, SNWLID-2026-0014, yourself. OpenCVE separately suggests risk reducers while you prepare: restrict SSL VPN access to trusted IP ranges, require SAML and MFA for all users while disabling alternative methods, and turn on detailed SSL VPN logging. Those reduce exposure. They are not a substitute for the patch.

Timeline of three dates: 6 November 2026 publication and CISA KEV listing, 9 November 2026 day three, and the 20 November 2026 US federal patch deadline

The 20 November date matters less than it looks. It binds US federal agencies. A flaw that is already being exploited sets its own deadline for everyone else, and that deadline is now.

The real gap is ownership

Think about how many firewalls in Indonesian businesses were installed by a vendor, handed over with a password, and never looked at again. A shop, a branch office, a cafe with a small VPN so the owner can reach the till system from home. Nobody there reads CISA alerts. Nobody knows whether the box runs 7.3.3 or 7.3.4. When a flaw like this lands in the KEV catalog, the first sign is not an alert. It is an odd entry in a log, if anyone is reading the log.

That is why the first question after a headline like this should be organisational, not technical: who holds the update schedule for our firewall? If the answer is a name and a date, you are in decent shape. If the answer is "the vendor", ask them in writing when they last checked and when they will check next.

What to check this week

  1. Find the exact SonicOS version on every SonicWall firewall you run, including the ones at branches.
  2. Check whether the SSL VPN uses SAML login, and whether other login methods are enabled alongside it.
  3. Compare your version with SNWLID-2026-0014 and plan the patch to the version it names.
  4. Assign one person and one date, then review the VPN logs from the past week for logins that never triggered an MFA prompt.
Four-step order of checks: find the version, check SAML login, match the advisory, schedule the patch

Make it a cycle

Patching once is not the goal. The next flaw is already somewhere in the queue, and it will not wait for a quarterly meeting. A small routine is enough: keep a list of every firewall and its version, watch the vendor advisories and the CISA KEV list, schedule updates in quiet hours with a named owner, confirm that VPN login and MFA still work afterwards, and record who did it and when.

Cycle of five steps around one accountable owner: record, watch, schedule, update, record again

If you are not sure where your firewall stands, we can help you check it. Reach us at bisnis@xetup.id or WhatsApp +62 822 6515 7644.

Sources