SONICWALL SSL VPN / CVE-2026-19868
A stolen password should not be enough to open your VPN.
An exploited SonicWall flaw can let valid alternate-login credentials bypass the sign-in route that enforces multi-factor authentication (MFA). Here is what to patch, what to check, and what your logs can actually tell you.
MFA only protects a login if the gateway requires the path that enforces it.
A virtual private network, or VPN, lets someone connect to an internal network from elsewhere. With CVE-2026-19868, a user holding valid credentials for an alternate authentication method may bypass the SAML controls on a SonicWall SSL VPN. That can also bypass the second factor enforced through SAML. SonicWall says the issue affects SSL VPN logins only when SAML is enabled.
SAML is the sign-in handoff from the firewall to an identity service, such as the organization’s central login provider. The service can require a second factor and return a signed response. This flaw can let a different accepted login method get around that handoff.
ALREADY ON CISA'S EXPLOITED LIST
Make the update a current task. CISA added this flaw to KEV on November 6, with a November 20 federal remediation deadline. That date applies to covered federal agencies; it is not a reason for other exposed organizations to wait.
One intended route. An alternate route around its check.
HOW THE GAP CHANGES A SIGN-IN
SAML WITH REQUIRED MFA
The important combination is an affected SonicOS build, SSL VPN configured for SAML, and valid credentials accepted through an alternate method. Review the configuration and effective access for your device. Do not assume that a SAML setting alone proves every accepted route enforces the same policy.
Check the gateway. Assign the update.
Record the appliance model, the full running firmware build (its installed software version), whether SSL VPN is enabled and reachable, and whether its authentication type is SAML. SonicWall's advisory covers both physical and virtual Gen7 and Gen8 platforms.
GEN7 / FIRST FIXED BUILD
SonicOS
Affected line: 7.3.3-7015 and older versions listed in the advisory.
GEN8 / FIRST FIXED BUILD
SonicOS
Affected line: 8.2.2-8015 and older versions listed in the advisory.
Use the platform table and fixed-software guidance to select the current supported target for the exact model. A short version label such as “7.3.4” is not enough for the change record. Verify the full build running after the update.
- 01 / OWN THE CHANGE
Name the owner.
Confirm the device, configuration backup, recovery plan, and approved maintenance window.
- 02 / APPLY THE FIX
Update and verify.
Install the applicable vendor fix. Check the running build and required sign-in policy after the change.
- 03 / REVIEW ACCESS
Check prior sessions.
Patching fixes the flaw. It does not establish what earlier sessions did or what they reached.
SonicWall lists no workaround. If the update cannot happen immediately, have the network owner assess restricting or suspending affected remote access and arrange an approved alternative for essential users. Treat that as temporary exposure reduction, not a substitute for the firmware fix.
If this gateway provides access to a plant, utility, or building system, check what VPN-authorized accounts can reach. That is the operational-technology connection: the remote-access route into the environment. It does not establish that this flaw has been used against an industrial process.
One session. Three records to compare.
Preserve the available records before retention expires or maintenance changes them. Start with successful VPN sessions, then compare identity-service evidence and activity inside the network.
Who connected?
Account, recorded source address, time, gateway, and available session details.
What policy ran?
The relevant application, sign-in result, MFA evidence, and any session reuse allowed by policy.
What happened next?
Resources reached, account activity, and endpoint or network evidence tied to the session.
It is not proof of bypass. Check log coverage, retention, clocks, username mapping, and legitimate session reuse before deciding that a sign-in skipped a required check. Keep an unknown result distinct from a confirmed policy failure.
Escalate sessions that conflict with the account's approved access or have suspicious follow-on activity. Preserve their evidence and use your incident process to contain access, revoke relevant sessions, and reset credentials where warranted.
FOR THE NETWORK OWNER AND RESPONDER
Take one gateway through the review.
The worksheet keeps the update, evidence references, and unresolved questions together. End with a named owner and a next action.
Download the one-page worksheetOpen the readable worksheetUse the events the gateway actually records
SonicWall documents event 1080, Successful SSLVPN User Login, in its SonicOS 7.X login-monitoring instructions. That is a useful starting set for an access review. The event does not, by itself, prove that SAML or MFA was bypassed.
Any syslog receiver: select the native login event
On an export restricted to your SonicOS firewalls, filter the native message-ID field m to the exact value 1080. Keep the original time, appliance identity, account, and source fields. Do not use a free-text search for the number alone.
The companion includes a small Python selector for one-event-per-line native key/value exports. It keeps the selected lines and separately reports missing IDs, duplicate IDs, and malformed quoting. It does not accept CEF, CSV, or JSON exports.
Elastic KQL: successful SSL VPN logins
In Discover, use the logs-sonicwall_firewall.log-* data view, set the investigation time range, select KQL, and run:
data_stream.dataset:"sonicwall_firewall.log" AND event.code:"1080"Add @timestamp, observer.serial_number, user.name, and source.ip as columns. The companion includes a second filter for events with appliance, account, and source fields present; compare it with the broader result so incomplete events stay visible.
Source prerequisite: the standard SonicWall Firewall integration must already parse your events correctly. Its documented compatibility names SonicOS 6.5 and 7.0. Verify event 1080 and the actual fields on 7.3 or 8.2 with an authorized normal login before relying on this query. Use the raw-event route if parsing is incomplete.
Review newly seen appliance/account/source combinations against your history and approved access. Account for new users, travel, changing network addresses, and support activity. Preserve the account realm and gateway identity. Elastic also supplies a first-seen remote-access rule; follow its current setup and history requirements if you use it.
Validation: the native selector was run against synthetic positive, negative, missing-data, and malformed-input fixtures. The KQL filters were checked against documented syntax and fixture matching expectations, not executed in Kibana or a customer tenant. These are access-review hunts, not a CVE-specific signature. No Deception Check schema or sensor feed is required.
Download the hunt companionRead the quickstart and source notes
Ask the useful question: can we show that this session met our required sign-in policy?
Sources and scope
- SonicWall SNWLID-2026-0014: conditions, fixed builds, no-workaround statement, and vendor exploitation notice.
- CISA KEV entry: November 6 addition and November 20 federal deadline. The catalog lists ransomware use as unknown.
- CVE record: vendor description and affected branch thresholds.
- SonicOS 8.2.3-8015 release notes: alternate-authentication enforcement fix, issue GEN8-18361.
The diagrams explain the advisory and the proposed investigation workflow. Log-hunt sources and validation limits are listed with the companion.
