Guide
CISA KEV additions, Nov 6 to Nov 9, 2026: what was added and how to triage
CISA's November 6 and November 9, 2026 alerts added five exploited CVEs to the KEV catalog. What the alerts say, what BOD 26-04 requires, and how to triage.
What CISA added on November 6 and November 9, 2026
CISA published two Known Exploited Vulnerabilities (KEV) alerts four days apart. Together they add five CVEs to the catalog. Both alerts give the same reason for each addition: evidence of active exploitation.
The November 6, 2026 alert adds a single entry, in SonicWall's SonicOS.
CISA lists that entry as CVE-2026-19868 and describes it as a use of single-factor authentication vulnerability in the SonicOS SSLVPN.
The November 9, 2026 alert adds four more entries to the catalog.
The first two in that alert are CVE-2026-102895, an improper authentication vulnerability in GPUStack, and CVE-2026-116779, a code injection vulnerability in SignalWire FreeSwitch.
The other two are CVE-2026-123158, an "unexpected status code or return value" vulnerability in OpenBSD OpenSSH, and CVE-2026-123218, an incorrect authorization vulnerability in IBM Aspera Faspex.
The five entries fall into these categories:
- SonicWall SonicOS SSLVPN (CVE-2026-19868): single-factor authentication, added November 6
- GPUStack (CVE-2026-102895): improper authentication, added November 9
- SignalWire FreeSwitch (CVE-2026-116779): code injection, added November 9
- OpenBSD OpenSSH (CVE-2026-123158): unexpected status code or return value, added November 9
- IBM Aspera Faspex (CVE-2026-123218): incorrect authorization, added November 9
Three of the five are authentication or authorization weaknesses: the SonicOS, GPUStack and Aspera Faspex entries. Neither alert gives affected version numbers, fixed versions, severity scores or details of the observed exploitation. Each alert names the product, the CVE ID and the weakness category, and nothing more.
How CISA frames the risk
Both alerts use nearly the same language to describe why these entries matter. The November 9 alert says the vulnerabilities pose significant risk to federal systems.
The November 6 alert uses the singular form of the same sentence for the SonicOS entry.
The alerts also restate CISA's criteria for adding an entry to the catalog. A candidate needs three things: a CVE identifier, evidence of exploitation, and clear mitigation guidance.
So for each of these five CVEs, CISA's own criteria mean that a CVE ID, evidence of exploitation and mitigation guidance existed when it was added. The alerts do not reproduce that guidance. A team will need to find the remediation details in the catalog entries or in the vendors' own materials.
What the alerts require, and of whom
Both alerts tie the catalog to a single directive. CISA describes Binding Operational Directive 26-04 as the source of vulnerability management requirements for civilian federal agencies.
According to the alerts, the directive gives the catalog a central role.
The core obligation is fast remediation of high-risk vulnerabilities.
The alerts define "high-risk" narrowly. The definition covers KEV-listed CVEs on publicly exposed assets where exploitation gives an attacker total control of the asset. Lower-risk items can wait.
Patching is not the only requirement. The directive also expects agencies to check whether a system was compromised before the fix went in.
The question of deadlines
The question asks "by when." Neither alert names a remediation due date for any of the five CVEs. Neither gives a timeline for the compromise checks that BOD 26-04 calls for. The alerts say only that the directive sets "basic expectations for when" agencies must check for prior compromise. The specific timelines sit in the directive itself, which these documents describe but do not quote.
Teams that track due dates should take them from the directive and the KEV catalog entries for these CVEs, not from these alerts. The alerts do confirm two dates: November 6, 2026 for the SonicOS entry and November 9, 2026 for the other four.
Who is bound, and what CISA asks of everyone else
The directive's legal reach is limited, and CISA says so directly. For other organizations, the alerts offer a recommendation rather than a mandate.
The same sentence goes on to encourage all organizations to prioritize remediation of KEV catalog vulnerabilities. For a private-sector security leader, then, these five CVEs carry no regulatory deadline from these alerts. They do carry CISA's statement that each one has been exploited.
Triage against your own environment
The alerts do not give step-by-step triage instructions. They do describe the risk test that BOD 26-04 applies, and CISA encourages all organizations to adopt that kind of risk-based approach. Applied to these five entries, the test reduces to four questions taken directly from the alert text.
1. Do we run it? Start with inventory. The five products are SonicWall SonicOS with SSLVPN, GPUStack, SignalWire FreeSwitch, OpenBSD OpenSSH and IBM Aspera Faspex. The alerts give no version ranges, so a match on product name is the first filter, not the last. OpenSSH may be the broadest search of the five, because it can appear on many hosts, not only as a single application.
2. Is it publicly exposed? The directive's high-risk definition depends on exposure. It covers KEV-listed CVEs "on publicly exposed assets." For each confirmed instance, record whether it can be reached from the internet. The SonicOS entry is listed against the SSLVPN component specifically, so the exposure check for that product should start with the SSLVPN.
3. Would exploitation give total control? The second part of the directive's test is whether a vulnerability grants "total control of the asset post-exploitation." The alerts list only weakness categories (code injection, improper authentication, incorrect authorization and the others) and do not say what an attacker gains. Teams will need the vendor or catalog details to answer this question for each CVE.
4. Was it already compromised? BOD 26-04 asks agencies to check whether attackers compromised a system before the patch was applied. Every entry here was added because of active exploitation. For any exposed, affected instance, a compromise review is part of the directive's model and does not stop once the patch is installed.
Instances that pass the first three questions match the directive's high-risk definition, which calls for rapid remediation. Under the same framework, instances that are internal or that would not give total control fall into the category the directive allows to be deferred.
Ongoing additions
These two alerts are part of a continuing process. CISA says the catalog will keep growing as new entries meet its criteria.
CISA also accepts nominations from outside the agency.
The alerts point readers to CISA's KEV Nomination Form for submissions. A nomination has to meet the same three criteria as any other entry: a CVE ID, evidence of exploitation and clear mitigation guidance.
Sources
By email, once a week
Get the week’s briefings on Friday
The week’s briefings and the new entries in CISA’s exploited-vulnerabilities catalog, in one email.
Unsubscribe any time.