~/f4n6 $ grep -r "SonicWall SSLVPN SAML bypass CVE-2026-19868 added to CISA KEV" ./investigations/ --include="*.md"

SonicWall SSLVPN SAML bypass CVE-2026-19868 added to CISA KEV

Jeff Davies 07 Nov 2026 5 min read

1. Executive summary

CVE-2026-19868 is a use of single-factor authentication flaw (CWE-308) in SonicWall SonicOS SSLVPN, rated CVSS 7.5 HIGH by NVD, that lets a user holding valid credentials for an alternate authentication method bypass SAML authentication controls and the SAML-enforced MFA that depends on them. CISA added it to the Known Exploited Vulnerabilities catalog with a remediation due date of 2026-11-20, which places it among vulnerabilities CISA states have been exploited in the wild. Any EMEA financial services firm terminating remote access through a SonicWall SSLVPN portal with SAML and MFA enforced is exposed: the control the firm relies on to gate VPN access can be sidestepped by anyone who already holds a working credential for a secondary authentication path. The risk is highest where the SSLVPN is internet-facing and where local or alternate accounts remain enabled alongside SAML, because that is the precondition the flaw turns into a bypass.

2. Regulatory framing

Article Trigger (the fact in this item) Practical impact
DORA Art. 19: reporting of major ICT-related incidents to competent authorities CISA records the flaw as exploited in the wild and it sits on an internet-facing remote access gateway, so a successful bypass is an ICT-related incident on a perimeter control If the bypass is used to reach the network, the firm must run the major-incident classification and, where it qualifies, the authority reporting process on the DORA timeline
DORA Art. 28: ICT third-party risk — general principles The exposure is in a third-party VPN product the firm depends on for remote access, and the fix depends on the vendor's instructions The firm must confirm the vendor mitigation path, track the vendor's guidance, and record the dependency and its remediation state in its third-party risk register
NIS2 Art. 21(2)(d): supply chain security measures The vulnerable component is supplied by SonicWall and the remediation is gated on the vendor's instructions Entities in scope must treat the vendor patch and mitigation status as a supply chain security item and verify it is applied

3. Technical analysis & attack chain

The flaw is a use of single-factor authentication weakness in SonicWall SonicOS SSLVPN. NVD describes it as allowing a user with valid credentials for an alternate authentication method to bypass SAML authentication controls, and states that successful exploitation may also bypass SAML-enforced multi-factor authentication. In practical terms the SSLVPN portal accepts a login through a path other than SAML, and because that path is treated as authenticated, the SAML policy and the MFA bound to it are not enforced for that session.

Confirmed steps, as far as public reporting supports them:

  1. The attacker holds valid credentials for an alternate authentication method on the SonicOS SSLVPN. How those credentials are obtained is not stated in public reporting.
  2. The attacker authenticates to the SSLVPN through that alternate method rather than through SAML.
  3. The SAML authentication controls are bypassed, and the SAML-enforced MFA is bypassed with them, so the session is established without the second factor the SAML policy would have required.

What the sources do not give: the affected SonicOS versions, the fixed release, the specific alternate authentication method or methods that trigger the bypass, the interface or endpoint involved, and any post-authentication activity. No fixed release is named in public reporting, and no vendor advisory detail beyond the NVD description is available here. The CISA entry directs defenders to apply mitigations in accordance with vendor instructions and to follow BOD 26-04 guidance, including discontinuing use of the product where mitigations are unavailable; it does not itself name a patch version.

The exploitation state rests on the CISA KEV listing, which records the CVE with a due date of 2026-11-20. CISA KEV does not state who is exploiting it, against whom, or with what post-access behaviour, and the entry records known ransomware campaign use as Unknown. No actor is named in any source for this CVE, and no MITRE ATT&CK profile is associated with it, so any attribution would be unconfirmed.

The related SonicWall SMA1000 items in the source set concern different products and different CVEs (CVE-2026-15410, CVE-2026-83548, CVE-2026-102255) and describe SSRF and code injection flaws in the SMA1000 appliance line, not the SSLVPN SAML bypass. They contribute no facts to this item and are noted only so the reader does not conflate the two product lines.

4. Mitigation & containment

P1 (within 24 hours)

  • Inventory every internet-facing SonicWall SonicOS SSLVPN portal and confirm which authentication methods are enabled. The bypass depends on an alternate method being available, so disable any local or non-SAML authentication path on the SSLVPN where the business does not require it, and record the decision.
  • Apply the vendor mitigations referenced by the CISA KEV entry in accordance with SonicWall's instructions. No fixed release is named in public reporting, so confirm the current guidance directly with SonicWall before relying on a version number.
  • Hunt SSLVPN authentication logs for sessions that authenticated through a non-SAML method, and for successful logins that did not complete an MFA challenge. Treat any such session as suspect and review what it reached.
  • Where mitigations cannot be applied, follow the CISA BOD 26-04 direction and discontinue use of the product for that exposure until a mitigation is available.

P2 (within 72 hours)

  • For accounts that can reach the SSLVPN by an alternate method, rotate credentials and require re-enrolment, since a valid alternate-method credential is the precondition for exploitation.
  • Restrict SSLVPN portal access by source geography or IP allow-list where operationally feasible, to shrink the population able to attempt the bypass.
  • Review MFA enforcement configuration to confirm SAML is the only path that grants SSLVPN access, and remove or disable any fallback that does not carry MFA.

P3 (within 7 days)

  • Add SSLVPN authentication events to continuous monitoring with alerting on non-SAML logins and on MFA-skipped sessions.
  • Record the SonicWall SSLVPN dependency and its remediation state in the third-party risk register, and set a review date tied to the vendor's patch guidance.

5. Indicators of compromise

No indicators of compromise available in the source material.

The sources describe no atomic indicators for this CVE. The observable signal is behavioural: an SSLVPN session that authenticated by a method other than SAML, or a successful SSLVPN login that did not complete the SAML-enforced MFA challenge.

Behavioural indicators

behaviour where to observe confidence
SSLVPN session authenticated through a non-SAML method SonicOS SSLVPN authentication and audit logs Medium; derived from the NVD description of the flaw, not from a named detection source
Successful SSLVPN login without a completed SAML-enforced MFA challenge SonicOS SSLVPN and MFA/IdP logs correlated by user and time Medium; derived from the NVD description, single-sourced to NVD

6. Detection

Insufficient indicators to author detection rules.

The sources give no file artefacts, command lines, paths, registry keys or traffic strings for this CVE. The usable signal is authentication behaviour, which is better expressed as the log correlation described in §5 than as a content-matching rule built from strings the sources do not provide.

CVE assessment

1 referenced CVE

CVE CVSS Exploited EPSS Summary
CVE-2026-19868 7.5 High — — An authentication enforcement vulnerability in SonicOS SSLVPN service may allow a user with valid credentials for an alternate…

7. Sources

  • NVD, CVE-2026-19868 detail, https://nvd.nist.gov/vuln/detail/CVE-2026-19868, published 2026-11-06
  • CISA Known Exploited Vulnerabilities entry for CVE-2026-19868, as reflected at https://nvd.nist.gov/vuln/detail/CVE-2026-19868, due date 2026-11-20

8. Adverse Trace position

Adverse Trace assesses CVE-2026-19868 as CVSS 7.5 HIGH per NVD, with exploitation confirmed by its CISA KEV listing and a remediation due date of 2026-11-20; the KEV entry records ransomware campaign use as Unknown and names no actor, so attribution is unconfirmed. For EMEA financial services clients the impact is concentrated on firms that expose a SonicWall SSLVPN portal with SAML and MFA and that also leave an alternate authentication method enabled, because that combination is what the flaw converts into a bypass of the control gating remote access. The technical detail here is single-sourced to NVD and CISA; no affected or fixed versions are named in public reporting, so clients should verify the vendor mitigation directly rather than rely on a version number from this note. We will track SonicWall's advisory for affected and fixed versions and update this note when they are published, and we will treat any client report of a non-SAML SSLVPN session as a potential incident under DORA Art. 19 classification.


Read the original source →

Published via PulseTrace — Adverse Trace threat intelligence.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies