CVE-2026-19868
Sonicwall Sonicos ≤ 7.3.4-7015
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-19868 is a high-severity Use of Single-factor Authentication (CWE-308) vulnerability in Sonicwall Sonicos. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Application Specific Passwords (T1697); ranked at the 46th percentile by exploit likelihood (below the median); CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-8 (Identification and Authentication (Non-organizational Users)) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-118429
Vulnerability Data
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).
- CWE(s)
- KEV Date Added
- 06 November 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4V6.3.6V6.4.2V6.4.3
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
ia-2 requires unique identification and authentication of users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
ia-8 requires unique identification and authentication of non-organizational users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Explicit MFA requirement directly eliminates single-factor authentication while the control also addresses broader authentication scope.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.5 directly mandates multi-factor authentication for critical information systems and requires authentication strength appropriate to information classification, which is exactly the remedy for CWE-308 (single-factor where more is required). When applied to a system that previously used single-factor authentication in a context requiring MFA, the weakness is removed — this is the 'mandates a measure removes the weakness that is the absence of that measure' pattern, and the clause's provisions cover the full scope of where CWE-308 applies.
A.8.29's functional authentication testing, code review, and penetration testing will expose most single-factor authentication weaknesses, but some instances in contexts where the need for a second factor is not explicitly required or is obscured in third-party components remain unfound.
A.5.17's password management (strong passwords, no reuse, blocking common/compromised passwords, secure storage/transmission, forced change on compromise) makes the single factor harder to compromise via guessing, brute-force, dictionary, and credential-stuffing attacks, but the single-factor weakness remains fully exploitable through phishing, keyloggers, social engineering, and credential-database theft — vectors that do not depend on password strength — and the clause never mandates a second factor.
Training technical teams on authentication requirements can influence architectural decisions to require multiple factors, but CWE-308 is a design-phase weakness where the choice of single-factor is often a deliberate architectural decision or default that training only partially counters; the effect is real but a minority one, similar to A.6.3 vs CWE-598.
A.6.7 guidance item (k) explicitly names single-factor authentication as a vulnerability to consider for remote access, so a well-implemented remote working policy would mandate multi-factor for remote access and remove that subset of CWE-308; however, the language is 'taking into consideration' rather than a direct mandate of multi-factor, the actual implementation requires other access-management controls, and CWE-308 extends beyond the remote-access context, leaving a nameable remainder.
A.8.2(f) explicitly addresses authentication strength for privileged access, stating that authentication requirements for privileged access rights can be higher (including re-authentication or step-up), so implementing the clause where single-factor auth was used for privileged access removes CWE-308 in that context; however, CWE-308 also arises in non-privileged contexts (normal user access, remote access, sensitive operations) that A.8.2's privileged-access scope does not reach.