CISA has placed a SonicWall SonicOS SSLVPN flaw, CVE-2026-19868, in its Known Exploited Vulnerabilities catalog. The catalog entry shows a date added of 2026-11-06 and a due date of 2026-11-20, per CISA.
CISA says a user with valid credentials for an alternate authentication method may be able to bypass SAML authentication controls.
Key facts
- The flaw: CISA lists CVE-2026-19868 as a SonicWall SonicOS SSLVPN use of single-factor authentication vulnerability.
- The dates: The catalog entry shows a date added of 2026-11-06 and a due date of 2026-11-20.
- The risk: CISA says valid credentials for an alternate authentication method may let a user skip SAML controls, and a successful attack may also defeat SAML-enforced multi-factor authentication.
- The fix: CISA tells organizations to follow the vendor's mitigation instructions while meeting BOD 26-04 and its forensic triage requirements.
- The fallback: If no mitigation is available, CISA says to follow BOD 26-04 guidance for cloud services or stop using the product.
Background
The KEV catalog is CISA's running list of flaws that attackers are already using. The entry for this SonicOS issue explains the core problem in plain terms. CISA said the SSLVPN feature relies on a single factor in a way that may let someone with working credentials for another sign-in method bypass SAML authentication. The agency added a second warning: "Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA)," CISA wrote.
The entry also points readers to more material. It links to the BOD 26-04 directive, the BOD 26-04 implementation guidance and the NVD page for CVE-2026-19868.
BOD 26-04 is titled Prioritizing Security Updates Based on Risk. CISA describes a Binding Operational Directive as a required order to federal executive branch departments and agencies to protect federal information and systems. The new directive replaces two older ones. CISA said BOD 26-04 supersedes and revokes BOD 19-02, dated April 29, 2019, and BOD 22-01, dated November 3, 2021, and pulls federal patching guidance into one place.
Under the directive, speed depends on risk. CISA said four factors set how urgent a fix is: asset exposure, KEV status, exploit automation and technical impact. Those factors feed a table called Table 1: Remediation Timelines, per the directive. The exact day counts in that table were not part of the material reviewed for this article, and neither were specific vendor patch-version details, which CISA said to take from vendor instructions.
The directive also defines what counts as exposed. CISA said a "publicly exposed" resource is any agency-owned or agency-managed IT resource that unauthenticated or untrusted parties can reach over public networks such as the internet, no matter where it sits physically or logically.
What it means for you
The directive is aimed at federal executive branch departments and agencies. CISA places the job of judging each asset's internet exposure on the stakeholders who run it.
Our cybersecurity services help teams find exposed remote access gear and close gaps like this one. For firms that work with government buyers, our public sector IT support covers patch tracking and reporting. A tested disaster recovery plan also limits the damage if an attacker does get in.
Practical steps
- Find every affected device. List each device running SonicOS SSLVPN, and note which ones can be reached from the internet.
- Follow the vendor's fix. CISA directs organizations to apply mitigations as the vendor instructs. Patch version details should come from the vendor's own guidance.
- Run forensic triage when the catalog calls for it. CISA's implementation guidance says that when the KEV catalog lists triage steps for a CVE, agencies should follow those steps, and it sets out forensic checks for a fast response.
- Meet the due date. CISA's FAQ tells agencies to fix a flaw by the dueDate that the BOD 26-04 Vulnerability Response Timeline table sets. For this entry, the catalog lists 2026-11-20.
- Have an exit plan. If no mitigation is available, CISA says to follow BOD 26-04 guidance for cloud services or stop using the product.
For a wider view of recent additions, see our post on other recently listed flaws.
What happens next
The directive rolls out in phases. CISA said Phase I took effect right away. It requires agencies to watch for KEV Catalog updates, fix flaws within KEV timelines and automate KEV status reporting through the Continuous Diagnostics and Mitigation Dashboard.
Reporting rules apply to agencies that are not there yet. CISA said agencies that have not fully automated reporting through the CDM Program must send status reports by hand every two weeks.
Later phases have set windows. The directive says Phase II comes within 60 days of issuance and Phase III within 180 days. In Phase III, CISA said agencies must fix each flaw as fast as they can and no later than the Table 1 timelines.
This article does not treat the flaw as known to be used in ransomware campaigns.



