Guide
CISA KEV additions, Nov 9 to Nov 10, 2026: what was added and how to triage
CISA added ten exploited CVEs to its KEV Catalog on November 9 and 10, 2026. Here is what was added and what BOD 26-04 asks teams to prioritize.
Two alerts, ten CVEs
CISA published two alerts on consecutive days, November 9 and November 10, 2026. Each alert added entries to the agency's Known Exploited Vulnerabilities (KEV) Catalog. The November 9 alert added four CVEs and the November 10 alert added six, for ten in total. In both alerts, CISA says the additions are based on evidence of active exploitation, not on severity scores or theoretical risk.
Both alerts use the same language to explain why the entries matter. They describe these types of vulnerabilities as a frequent attack vector for malicious cyber actors and say they pose significant risks to the federal enterprise.
The alerts themselves are short. Each lists the CVE identifier, the vendor and product, and a one-line weakness description. Each then points readers to the binding directive that governs federal remediation. The sections below cover the entries first, then the directive, because the directive is where the alerts set out how remediation should be prioritized.
The November 10, 2026 additions
The larger of the two alerts lists six CVEs from five vendors. Barracuda Networks appears twice. The entries, in the order CISA lists them:
- CVE-2026-20320, Cisco BroadWorks, an improper restriction of XML external entity reference vulnerability.
- CVE-2026-111560, Barracuda Networks, an OS command injection vulnerability affecting multiple products.
- CVE-2026-111793, Openwave Messaging Limited Webtop Media Transcoder, an incorrect resource transfer between spheres vulnerability.
- CVE-2026-116606, Barracuda Networks Email Security Gateway (ESG), an authentication bypass using an alternate path or channel.
- CVE-2026-124194, Microsoft Office Outlook, a missing user interaction for potentially unsafe action vulnerability.
- CVE-2026-125350, Google Chromium, a use-after-free vulnerability.
The alert does not list affected versions, fixed versions or vendor bulletin details for any of these six entries. Teams building a ticket for each one will need the matching KEV Catalog record and the vendor's own guidance to fill in those fields.
The November 9, 2026 additions
The earlier alert lists four CVEs, each from a different vendor. The entries, in CISA's order:
- CVE-2026-102895, GPUStack, an improper authentication vulnerability.
- CVE-2026-116779, SignalWire FreeSwitch, a code injection vulnerability.
- CVE-2026-123158, OpenBSD OpenSSH, an unexpected status code or return value vulnerability.
- CVE-2026-123218, IBM Aspera Faspex, an incorrect authorization vulnerability.
As with the November 10 alert, the entries carry only the identifier, product and weakness type. The alert gives no technical detail on how each flaw is being exploited, and it does not attribute the exploitation to any actor.
What the alerts say about deadlines
Neither alert states a remediation due date for any of the ten CVEs. Neither sets a fixed number of days for patching. Instead, both alerts tie remediation expectations to a binding directive for federal civilian agencies. CISA's alerts say Binding Operational Directive (BOD) 26-04, titled "Prioritizing Security Updates Based on Risk," sets the vulnerability management requirements for those agencies.
For a security leader, that means the alert text alone does not answer the question of when each item must be closed. The timing for federal agencies comes from BOD 26-04 and the KEV Catalog entries it references, not from the alert pages. Teams tracking a date should take it from those sources rather than from the release date of the alert.
How BOD 26-04 frames prioritization
The alerts summarize BOD 26-04 as a risk-based model rather than a "patch everything in the catalog" rule. According to both alerts, the directive requires agencies to prioritize rapid remediation of KEV-listed CVEs on publicly exposed assets where exploitation grants total control of the asset, and to defer action on lower-risk vulnerabilities.
That description gives three tests for triaging the ten new entries. The first is whether the CVE is in the KEV Catalog, which all ten now are. The second is whether the affected asset in a given environment is publicly exposed. The third is whether exploitation would grant total control of that asset. The alerts do not say which of the ten CVEs meet the second and third tests. That answer depends on where each product sits in an organization's own environment and on the exploitation outcome described in the catalog record or vendor guidance.
The directive also adds a step beyond patching. Both alerts say BOD 26-04 sets basic expectations for when agencies must check whether a system was compromised before the fix went on. Because every entry in these two alerts was added on evidence of active exploitation, that compromise check is part of the remediation work the directive describes, not an optional extra. The alerts do not spell out the specific triggers for the check. Those sit in the directive itself.
What applies outside federal agencies
BOD 26-04 binds only federal civilian executive branch agencies. CISA's alerts still urge every organization to adopt risk-based vulnerability management and to prioritize fixing vulnerabilities listed in the KEV Catalog. For private-sector and state and local teams, the practical reading of the two alerts is the same prioritization logic the directive applies to federal agencies. Start with KEV-listed CVEs on exposed assets where exploitation means full control, then handle lower-risk items afterward.
The alerts also describe how the catalog grows. CISA says it will keep adding vulnerabilities that meet its stated criteria. Organizations that see exploitation of a flaw not yet listed can nominate it, and both alerts give the bar a nomination has to clear: a CVE ID, evidence of exploitation and clear mitigation guidance.
Taken together, the November 9 and November 10, 2026 alerts give security leaders ten confirmed-exploited CVEs, a federal directive that ranks them by exposure and impact rather than by catalog order, and an expectation of a compromise check where a system was exploitable before patching. The specific due dates and version details are not in the alert pages. They have to be pulled from the KEV Catalog records and vendor guidance for each entry.
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.