How severe is CVE-2026-19868?

No CVSS score has been assigned to CVE-2026-19868 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-19868?

Affected package information for CVE-2026-19868 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-19868?

The records we use list no fixed release for CVE-2026-19868. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-19868 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-19868 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-19868 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-19868 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

Is CVE-2026-19868 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-19868 (SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-11-06. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-11-20. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-19868?

CVE-2026-19868 is classified as CWE-308 (CWE-308). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-19868 published, and has it been updated?

CVE-2026-19868 was published on November 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-19868

CVE-2026-19868 is a CWE-308 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-11-06) — treat it as actively exploited and patch now. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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.…

Published

Nov 6, 2026

Updated

Nov 6, 2026

Affected

—

Patched

—

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-11-06. Federal agencies were required to remediate by 2026-11-20.

Exploitation and automatability from CISA’s KEV catalog for CVE-2026-19868.

Description

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).

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
The records we use list no fixed release for CVE-2026-19868. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-19868 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works