CVE-2026-19868
CVE-2026-19868 — SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability
An authentication enforcement vulnerability in SonicOS SSLVPN service may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls. Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA).
Published Updated Sources: NVD, SonicWall (CNA), CISA, GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Nov 6, 2026
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.5
high
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade SonicOS to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Federal deadline Nov 20, 2026 — in 3 days
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
High
Integrity
Low
Scope
Changed
Attack Complexity
High
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | high | 2.2 | 4.7 | CNA, GHSA |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-308 · Use of Single-factor Authentication
- Bypass Protection Mechanism
Mitigation: Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise.::
Weakness & attack patterns
- CWE-308
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1110.001Brute Force: Password Guessing
- T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
- T1110.002Brute Force: Password Cracking
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Nov 6, 2026
Federal deadline
Nov 20, 2026
in 3 days
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable SonicOS.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added to CISA KEV catalog
Nov 6, 2026 · CISA
Added · CVSS 3.1 7.5 (AV:N)
Nov 6, 2026 · NVD
Initial · CVE published
Nov 6, 2026 · NVD
Added · GHSA-mq8w-j7h6-7q9w published (high)
Nov 6, 2026 · GitHub Security Advisory
CVE published by NIST.
Nov 6, 2026 · SOCRadar CTI
References
6 on the record
- psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014
Vendor Advisory, NIST
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868
US Government Resource, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-19868
NVD, Vendor Advisory
- github.com/advisories/GHSA-mq8w-j7h6-7q9w
Exploit, Third Party Advisory
- www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
- www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource
Coverage
3 stories from the feeds we poll
Exploited SonicWall SSL-VPN flaw lets attackers bypass SAML-enforced MFA (CVE-2026-19868)
Help Net Security · Nov 9, 2026
CISA Flags SonicWall SonicOS MFA Bypass Flaw Amid Reports of Possible Exploitation
The Hacker News · Nov 9, 2026
SonicWall Patches Exploited SonicOS Vulnerability That Weakens VPN Logins
SecurityWeek · Nov 7, 2026
Elsewhere on this site
- SonicWallevery CVE for this vendor
- SonicOSevery page on this product
- November 2026what else CISA listed
- Unclassifiedsame class
- CWE-308other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-19868 is SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability, a high vulnerability affecting SonicOS from SonicWall. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.