Skip to content

CVE-2026-19868: SonicWall SonicOS SSLVPN SAML Single-Factor Authentication Bypass

Density:
C-Level Executive Briefing CVE-2026-19868 CRITICAL SCORE 96/100

A critical authentication enforcement vulnerability in SonicWall SonicOS SSLVPN (Gen 7 and Gen 8 appliances) has been cataloged in the CISA Known Exploited Vulnerabilities (KEV) catalog following confirmed active in-the-wild exploitation. When an enterprise deploys SAML 2.0 Identity Provider (IdP) integration for Single Sign-On and Multi-Factor Authentication (MFA), an architectural flaw in the SonicOS authentication state machine permits remote attackers who supply valid single-factor credentials (such as local database accounts, RADIUS, or directory accounts) to bypass the mandatory SAML redirection and assertion exchange. SonicOS erroneously marks the connection state as authenticated, granting direct access to internal subnets via NetExtender tunnels. Given that stolen single-factor credentials from historical breaches can be converted directly into unrestricted internal corporate network access, Hermes scores CVE-2026-19868 at HTS 96 (CRITICAL).

HYBRID

HERMES THREAT SCORE & PERIMETER GATEWAY MFA INTEGRITY EVALUATION

Target: SonicOS SSLVPN Authentication State Machine (SAML 2.0 / IdP Integration)
Confidence: 98%
96 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 19 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

[object Object]

On November 6, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-19868 to its Known Exploited Vulnerabilities (KEV) catalog, mandating remediation across federal systems under Binding Operational Directive (BOD) 22-01. The vulnerability is an authentication enforcement failure (CWE-308) impacting SonicWall SonicOS firmware running on Generation 7 and Generation 8 hardware firewalls and virtual appliances (TZ, NSa, NSsp, and NSv series).

SonicWallโ€™s Product Security Incident Response Team (PSIRT) disclosed the flaw under security advisory SNWLID-2026-0014, noting in-the-wild exploitation by advanced initial access brokers (IABs) and ransomware affiliates targeting corporate networks. By submitting credentials valid under legacy or alternate local schemes against specific SSLVPN endpoints, attackers suppress the SAML redirection logic, successfully authenticating into the corporate VPN without triggering the mandated secondary factor (TOTP, push notification, or hardware token).

flowchart TD
subgraph External["External Untrusted Zone"]
Attacker["Threat Actor / IAB"]
StolenCreds["Single-Factor Credentials\n(Password Spray / Leaked DB)"]
end
subgraph Perimeter["Perimeter Gateway (SonicWall SonicOS)"]
WAN["WAN Interface :4433 / :443"]
StateEngine{"Auth State Machine\nsslvpn_process_auth()"}
SAMLMode{"SAML Enforced\nPolicy Active?"}
FallbackPath["Legacy Auth Branch\n(Local DB / RADIUS)"]
Bypass["Session Flag: AUTH_VALIDATED\n(Bypasses SAML Assertion)"]
end
subgraph Internal["Internal Corporate Network"]
LAN["Internal Subnets / Domain Controllers"]
Tunnel["PPP / NetExtender SSLVPN Tunnel"]
end
Attacker -->|Supplies User+Pass| WAN
StolenCreds --> Attacker
WAN --> StateEngine
StateEngine --> SAMLMode
SAMLMode -->|Alternate Scheme Injected| FallbackPath
FallbackPath --> Bypass
Bypass --> Tunnel
Tunnel --> LAN

The vulnerability resides within the SSLVPN authentication dispatcher in SonicOS firmware (sslvpn/auth_handler.c). In standard configurations, when an administrator enables SAML authentication for SSLVPN, all incoming connections received at /cgi-bin/sslvpnclient or /auth.cgi are required to follow the SAML Web Browser SSO Profile:

  1. The client issues an unauthenticated HTTP GET to the portal.
  2. SonicOS acts as the Service Provider (SP), generating an AuthnRequest and redirecting the browser (HTTP 302) to the enterprise Identity Provider (IdP).
  3. The IdP authenticates the user, enforces MFA, and posts a signed SAML Response containing an assertion back to the SonicOS ACS URL (/saml/sso).
  4. SonicOS verifies the cryptographic signature of the assertion and provisions the session.

However, SonicOS retains backward-compatibility logic supporting multiple concurrent authentication methods (local user database, RADIUS, and LDAP). In vulnerable firmware revisions, the incoming authentication state handler fails to verify that the active realm policy forbids non-SAML credential processing when handling direct POST requests.

Flawed Authentication Dispatcher (Decompiled C Reconstruction)

Section titled โ€œFlawed Authentication Dispatcher (Decompiled C Reconstruction)โ€
/* Decompiled representation from SonicOS sslvpn_core.so */
int sslvpn_process_auth(http_req_t *req, sslvpn_session_t *sess) {
int auth_result = AUTH_FAILED;
char *auth_method = http_get_param(req, "authMethod");
char *username = http_get_param(req, "userName");
char *password = http_get_param(req, "password");
/* Vulnerability Check: Policy check is bypassed if credentials match an alternate source */
if (g_sslvpn_config.saml_enforced) {
/* Intended: Reject any direct password POST and force SAML redirect */
if (auth_method == NULL || strcmp(auth_method, "SAML") != 0) {
/* VULNERABILITY: If the administrator left fallback local accounts active,
or if authMethod specifies 'local' / 'radius', the handler falls through
to legacy verification instead of returning 403 or redirecting to IdP. */
if (g_sslvpn_config.allow_alternate_schemes && auth_method != NULL) {
auth_result = authenticate_against_backend(auth_method, username, password);
if (auth_result == AUTH_SUCCESS) {
/* CRITICAL FLAW: Session is stamped as fully authenticated without MFA */
sess->auth_state = AUTH_STATE_VALIDATED;
sess->user_privileges = lookup_user_privileges(username);
return SSLVPN_OK;
}
}
return send_saml_redirect(req, sess);
}
}
return process_saml_assertion(req, sess);
}

Because sess->auth_state = AUTH_STATE_VALIDATED is committed into the global session table without validating the SAML token or triggering a secondary RADIUS challenge, the client receives a valid session cookie (SSLVPN_SESSION_ID). With this cookie, the client initializes the Point-to-Point Protocol (PPP) over HTTPS tunnel, receiving an internal IP address and full routing into the internal network.


Exploitation is conducted in three rapid stages over standard HTTPS (ports 443 or 4433):

sequenceDiagram
autonumber
actor Attacker as Threat Actor
participant GW as SonicWall SonicOS SSLVPN
participant IdP as Corporate IdP (Okta / Entra)
participant LAN as Internal Domain Controller
Note over Attacker,GW: Phase 1: Authentication Probe & Policy Check
Attacker->>GW: GET /cgi-bin/sslvpnclient (User-Agent: Mozilla/5.0)
GW-->>Attacker: HTTP 302 Redirect to IdP (SAML SSO enforced)
Note over Attacker,GW: Phase 2: MFA Downgrade & Direct Credential POST
Attacker->>GW: POST /auth.cgi (userName=jdoe&password=Password1!&authMethod=local)
Note over GW: sslvpn_process_auth() matches fallback backend
GW->>GW: Local/LDAP single-factor verification succeeds
Note over GW: FLAW: AUTH_STATE_VALIDATED set without IdP contact
GW-->>Attacker: HTTP 200 OK (Set-Cookie: SSLVPN_SESSION_ID=a8f9c1...)
Note over Attacker,LAN: Phase 3: Tunnel Establishment & Lateral Movement
Attacker->>GW: GET /sslvpn/tunnel (Cookie: SSLVPN_SESSION_ID=a8f9c1...)
GW-->>Attacker: Established PPP/SSL Tunnel (Assigned IP 10.100.1.45)
Attacker->>LAN: Kerberoasting / SMB Enumeration on Internal LAN
  1. Target Identification: The threat actor identifies internet-facing SonicWall firewalls running SSLVPN via banner grabbing or response headers (Server: SonicWALL).
  2. Credential Sourcing: Single-factor usernames and passwords obtained from dark-web credential dumps or enterprise password spraying are compiled.
  3. MFA Bypass Request: The attacker sends an HTTP POST to /auth.cgi or /cgi-bin/sslvpnclient, specifying parameters that trigger the alternate single-factor evaluation code path.
  4. Session Token Acquisition: The appliance responds with an authenticated SSLVPN_SESSION_ID cookie, bypassing the SAML Identity Provider completely.
  5. Tunnel Activation: Using the SonicWall NetExtender CLI or standard openconnect clients, the attacker establishes a virtual network interface and accesses internal enterprise systems.

Because the attack bypasses the cloud IdP, detection must focus on SonicWall syslog feeds, firewall connection logs, and network traffic passing through the SSLVPN virtual adapter.

title: SonicWall SonicOS SSLVPN SAML MFA Bypass Attempt
id: 5e91c784-2104-4df8-9b8e-cve202619868
status: experimental
description: Detects HTTP POST requests to SonicWall SSLVPN login endpoints attempting single-factor authentication override while SAML is active.
references:
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
author: Hermes Codex Cyber Defense Team
date: 2026-11-07
logsource:
category: webserver
product: sonicwall
detection:
selection_endpoint:
cs-method: 'POST'
cs-uri-stem|contains:
- '/cgi-bin/sslvpnclient'
- '/auth.cgi'
- '/cgi-bin/userLogin'
selection_params:
cs-uri-query|contains:
- 'authMethod=local'
- 'authMethod=radius'
- 'authMethod=ldap'
condition: selection_endpoint and selection_params
falsepositives:
- Legitimate administrative fallback logins from internal management subnets (filter by source IP).
level: critical
tags:
- attack.initial_access
- attack.t1133
- attack.t1556
- cve.2026.19868

Organizations operating SonicWall firewalls must execute immediate firmware upgrades and verify SSLVPN configuration settings.

Apply the official maintenance releases provided by SonicWall PSIRT:

  • SonicOS Gen 7 Appliances (TZ, NSa, NSsp, NSv): Upgrade to version 7.3.4-7013 or later.
  • SonicOS Gen 8 Appliances: Upgrade to version 8.2.3-8015 or later.

If brief scheduling windows precede emergency firmware flashing, organizations should enforce the following temporary containment controls:

  1. Disable Fallback Authentication Realms: Navigate to Device > Users > Settings > Authentication. Ensure that when SAML is selected as the primary authentication protocol, all secondary fallback mechanisms (Local Users, RADIUS, LDAP) are strictly disabled for the SSLVPN client portal.
  2. Restrict SSLVPN Source Access: Under Network > Firewall Rules, restrict incoming connections to WAN IP addresses on port 4433 to authorized geographic regions (Geo-IP filter) or pre-approved client IP ranges.
  3. Terminate Dormant Accounts: Audit and remove dormant local administrator and test accounts on the firewall itself to prevent single-factor credential stuffing against fallback paths.