Skip to content
CVE-2026-19868 Google Chronicle · YARA-L

Detect SonicWall SonicOS SSLVPN Single-Factor Authentication Bypass (CVE-2026-19868) in Google Chronicle

Detects exploitation and exposure indicators for CVE-2026-19868, an authentication enforcement weakness (CWE-308) in SonicWall SonicOS SSLVPN. A user with valid credentials for an alternate authentication method can bypass SAML authentication controls, and successful exploitation can also bypass SAML-enforced multi-factor authentication. This CVE is on the CISA KEV catalog. The detection surfaces successful SSLVPN authentications that lack a corresponding MFA/TOTP challenge, anomalous geolocation and impossible-travel logons, high-volume credential-stuffing against the SSLVPN portal, and post-authentication lateral movement that commonly follows VPN compromise.

MITRE ATT&CK

Tactic
Initial Access Credential Access Stealth

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
// df00tech DF00-809873f79f · https://df00tech.com/detections/CVE-2026-19868 · licence: https://df00tech.com/detections/licence
rule sonicwall_sslvpn_single_factor_auth_cve_2026_19868 {
  meta:
    author = "Argus Detection Platform"
    description = "SonicOS SSLVPN successful login without MFA/TOTP (CVE-2026-19868)"
    severity = "HIGH"
    cve = "CVE-2026-19868"
  events:
    $e.metadata.vendor_name = "SonicWall"
    $e.metadata.event_type = "USER_LOGIN"
    $e.security_result.action = "ALLOW"
    re.regex($e.metadata.description, `(?i)SSLVPN|SSL VPN`)
    not re.regex($e.metadata.description, `(?i)TOTP|one-time password|second factor|MFA`)
    $user = $e.principal.user.userid
  match:
    $user over 5m
  condition:
    $e
}
high severity medium confidence

Chronicle YARA-L rule matching SonicWall SonicOS SSLVPN allowed user logins whose description lacks MFA/TOTP indicators, flagging single-factor authentication (CVE-2026-19868).

Data Sources

SonicWall SonicOS syslog (Chronicle forwarder)UDM USER_LOGIN events

Required Tables

udm.events

False Positives & Tuning

  • MFA step recorded in a separate UDM event not evaluated by this rule
  • MFA-exempt accounts
  • Parser mapping variations across SonicOS firmware versions

Other platforms for CVE-2026-19868


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.

  1. Test 1 SSLVPN password-only authentication (single factor)

    Expected signal: SonicOS SSLVPN log shows a successful 'User login' / authenticated event for labuser from the test source IP with no corresponding TOTP/OTP acceptance entry.

  2. Test 2 SSLVPN credential stuffing against the portal

    Expected signal: Multiple SSLVPN authentication attempts for distinct usernames from one source IP within a short window.

  3. Test 3 NetExtender single-factor connect from new geolocation

    Expected signal: SonicOS logs a NetExtender SSLVPN tunnel establishment for labuser with a virtual-IP assignment and no OTP/TOTP acceptance event.


Response Playbook

Triage

  1. Confirm the affected SonicWall appliance firmware against SNWLID-2026-0014 and determine whether SSLVPN MFA enforcement was actually configured and active at the time of the logins.
  2. For each flagged VPN user, review the source IP geolocation, ASN, and hosting/VPN reputation; compare against the user's historical logon locations for impossible travel.
  3. Correlate the SSLVPN session with downstream activity (internal RDP/SMB, domain authentications, mailbox access) in the 60 minutes after login to assess whether access was used.
  4. Check whether the credentials appear in known infostealer/credential-dump feeds, which is a common precursor to KEV exploitation of this class.

Containment

  1. Enforce mandatory MFA on the SSLVPN portal and disable any single-factor or MFA-exempt authentication paths; apply the SonicWall fixed firmware from SNWLID-2026-0014.
  2. Terminate active SSLVPN sessions for the affected user(s), reset their credentials, and temporarily restrict SSLVPN access to known-good source IP ranges or geofenced regions pending investigation.

Evidence Collection

  1. Export the full SonicOS SSLVPN authentication log, firewall session log, and configuration backup (showing MFA policy state) for the investigation window and preserve them with hashes.
  2. Capture downstream host and identity-provider logs for sessions originating from the flagged VPN source IPs to document lateral movement and scope.

Escalation Criteria

  • !Escalate to incident response if a flagged single-factor login is followed by lateral movement, privilege escalation, or access to sensitive systems from the VPN-assigned IP.
  • !Escalate if the source IP is attributed to known threat infrastructure, matches KEV-associated indicators, or if multiple accounts authenticated single-factor from the same external IP (credential stuffing).

Investigation Guide

Forensic Artifacts

  • >SonicOS SSLVPN authentication and session logs (user, source IP, assigned virtual IP, timestamps)
  • >Firewall configuration backup showing SSLVPN MFA/OTP policy state
  • >NetExtender/Mobile Connect client connection records and DHCP lease assignments for the VPN pool

Tuning Guidance

Baseline legitimate MFA-exempt accounts (service/break-glass) and allowlist them explicitly rather than widening the MFA keyword filter. Ensure MFA/TOTP acceptance events are ingested into the same index/table the correlation joins against, otherwise every login appears single-factor; validate the SonicOS firmware's log format and adjust the usr=/src= parsing accordingly. Tighten the geofence and impossible-travel thresholds to your workforce's normal travel profile to reduce benign new-location noise.


Hunting Queries

Hunts for credential-stuffing / password-spray patterns against the SSLVPN portal by flagging source IPs authenticating against many users or at high volume per hour.

Hunting — KQL
kql
// df00tech DF00-809873f79f · https://df00tech.com/detections/CVE-2026-19868 · licence: https://df00tech.com/detections/licence
CommonSecurityLog | where DeviceVendor has "SonicWall" and Message has "SSLVPN" and Message has_any("login","authenticated") | summarize Users=dcount(SourceUserName), Attempts=count() by SourceIP, bin(TimeGenerated, 1h) | where Users >= 5 or Attempts >= 50 | order by Attempts desc
Hunting — SPL
spl
``` df00tech DF00-809873f79f · https://df00tech.com/detections/CVE-2026-19868 · licence: https://df00tech.com/detections/licence ```
index=firewall sourcetype="sonicwall:sonicos" "SSLVPN" ("login" OR "authenticated") | bucket _time span=1h | stats dc(vpn_user) as users count as attempts by src_ip _time | where users>=5 OR attempts>=50 | sort - attempts

Atomic Red Team Tests

Test 1 SSLVPN password-only authentication (single factor)
linux

Authenticate to the SonicWall SSLVPN portal with only a username and password, omitting any second-factor prompt, to generate a single-factor login event in a lab.

Command

bash
curl -sk -c /tmp/swl.cookie -d 'username=labuser&password=LabP@ss123&domain=LocalDomain' 'https://sslvpn.lab.example.com/auth.html' -o /tmp/swl_login.html

Cleanup

bash
rm -f /tmp/swl.cookie /tmp/swl_login.html

Expected Telemetry

SonicOS SSLVPN log shows a successful 'User login' / authenticated event for labuser from the test source IP with no corresponding TOTP/OTP acceptance entry.

Expected Detection

The KQL/SPL correlation flags labuser as a login with zero MFA events within the 5-minute window.

Test 2 SSLVPN credential stuffing against the portal
linux

Send repeated SSLVPN authentication attempts for multiple usernames from a single source to simulate credential stuffing enabled by single-factor auth.

Command

bash
for u in alice bob carol dave eve; do curl -sk -d "username=$u&password=Winter2026!&domain=LocalDomain" 'https://sslvpn.lab.example.com/auth.html' -o /dev/null; done

Cleanup

bash
echo 'no artifacts to remove (stateless requests)'

Expected Telemetry

Multiple SSLVPN authentication attempts for distinct usernames from one source IP within a short window.

Expected Detection

The hunting query flags the source IP for authenticating against >=5 users in one hour.

Test 3 NetExtender single-factor connect from new geolocation
windows

Establish an SSLVPN tunnel using the NetExtender CLI with password-only credentials from an atypical source to simulate anomalous single-factor VPN access.

Command

powershell
"C:\Program Files\SonicWall\SSL-VPN\NetExtender\NECLI.exe" connect -s sslvpn.lab.example.com -u labuser -p LabP@ss123 -d LocalDomain

Cleanup

powershell
"C:\Program Files\SonicWall\SSL-VPN\NetExtender\NECLI.exe" disconnect

Expected Telemetry

SonicOS logs a NetExtender SSLVPN tunnel establishment for labuser with a virtual-IP assignment and no OTP/TOTP acceptance event.

Expected Detection

The detection flags the login as single-factor; geolocation/impossible-travel triage surfaces the atypical source.

Related Detections