The 7 November batch carries seven SonicWall SonicOS records, all from one advisory that SonicWall published on 6 November 1. One of them, CVE-2026-19868, is on the KEV catalog with a 20 November remediation deadline, and SonicWall states its PSIRT investigated a report indicating potential exploitation 12. The other six score between 5.2 and 8.8 and come with the same fix, so the batch is one upgrade rather than seven projects.

The SSLVPN bypass with active exploitation

I wrote the flaw up on 8 November, and that post carries the advisory’s SAML scope condition, the 7.1 from SonicWall against the 7.5 on the CISA-ADP record, the fixed builds, and the authentication inventory I run: CVE-2026-19868 is a 7.5 from CISA-ADP and a 7.1 from SonicWall.

CISA added the record to the catalog on 6 November with a due date of 20 November, and the full catalog holds none of the other six 2. cve.now tracks one proof of concept on GitHub 3. Where the firmware cannot land by that date, I would ask the owner to switch off the alternate authentication methods on the SSLVPN first, since that change does not wait on the upgrade.

Two 8.8s on the management interface

CVE-2026-107155 rates 8.8. The advisory describes a permissive cross-domain policy in the management interface that, in specific conditions, could potentially enable a remote unauthenticated attacker to perform unauthorized operations 1. Its vector carries user interaction and no privileges required, so the first move belongs to an administrator who opens a page 1. My reading is that a page from an untrusted origin reaches the interface when an administrator has a management session open in the same browser, and the policy is the part that is misconfigured. The advisory gives no request sequence, and I have not tried to reconstruct one.

CVE-2026-107154 also rates 8.8 and sits in session validation. The interface relies on the client IP address as part of deciding whether a session is valid 1. Someone who can send traffic from the same address can ride a session they did not create, and the advisory scores it as a remote unauthenticated path to unauthorized operations 1.

I would also narrow who can reach the management interface while the patch rolls out. If the interface answers only on an internal segment, fewer people can open it, and exploiting either of those two still takes someone opening a page.

Denial of service in three records

CVE-2026-82308 is the most reachable of the three. It is a heap buffer overflow in the SSL-VPN service, before authentication, at low complexity 1. Anyone who can reach the VPN port can send the traffic, so I would expect scans for it. The impact stops at a denial of service, which is bad enough on an edge device that terminates remote access for everyone.

The two TACACS+ overflows, CVE-2026-77708 and CVE-2026-77709, rate 5.9 because the advisory scores high attack complexity on both 1. They land before authentication in the TACACS+ client, one on the stack and one on the heap, and both end in a denial of service 1. A firewall that authenticates administrators against a TACACS+ server carries the exposure; one that does not never runs the code.

A credential on the virtual appliances

CVE-2026-19703 applies to the NSv virtual appliances and starts from local access 1. Weak password hashing lets someone with that access recover a platform credential, and the credential reaches a limited subset of platform settings 1. This one needs a foothold first, so it sorts last in the relay. On a virtual appliance, local access runs through the hypervisor and the console, which puts that part with a different owner than the firewall.

The order I would send

Seven records, one advisory, one firmware line per generation, so the change is a single upgrade. I would lead with CVE-2026-19868 and the 20 November date, then note that the same build closes the other six 1. With that lead I would request the SSLVPN authentication method list, because I read it to decide whether the exploited flaw applies to a given firewall. That check takes a configuration read rather than a scan.

I will keep an eye on the catalog for the other six. If CISA lists any of them, I would move the rest of the advisory to the front with the exploited bug.


  1. SonicWall. (2026, November 6; last updated November 9). SonicWall SonicOS affected by multiple vulnerabilities (SNWLID-2026-0014). SonicWall PSIRT. https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  2. Cybersecurity and Infrastructure Security Agency. (2026, November 6). Known exploited vulnerabilities catalog (catalog version 2026.11.06). CISA. https://www.cisa.gov/known-exploited-vulnerabilities-catalog ↩︎ ↩︎

  3. cve.now. (2026, November 6). CVE-2026-19868: SonicWall SonicOS auth bypass in SSLVPN. cve.now. https://cve.now/CVE-2026-19868 ↩︎