cisaregulatorNewsThe Broadside1 min read

CISA adds four exploited CVEs to KEV Catalog

BOD 26-04 makes exposure and post-exploitation control the sorting criteria, which is useful only if agencies know their inventory.


TL;DR

CISA added four CVEs to the Known Exploited Vulnerabilities Catalog on Nov. 9, citing evidence of active exploitation: GPUStack, SignalWire FreeSwitch, OpenBSD OpenSSH, and IBM Aspera Faspex flaws. Binding Operational Directive 26-04 applies to Federal Civilian Executive Branch agencies, requiring prioritized rapid remediation for KEV-listed CVEs on publicly exposed assets that grant total control after exploitation. It doesn't apply to everyone else, though CISA urges broader risk-based vulnerability management.

CISA’s Nov. 9 update adds four vulnerabilities to the Known Exploited Vulnerabilities Catalog: CVE-2026-102895 in GPUStack, CVE-2026-116779 in SignalWire FreeSwitch, CVE-2026-123158 in OpenBSD OpenSSH, and CVE-2026-123218 in IBM Aspera Faspex. CISA says the additions are based on evidence of active exploitation, which is the part that should move them above ordinary scan noise for affected federal teams.

The compliance hook is Binding Operational Directive 26-04, not because it created this catalog entry, but because it sets vulnerability management requirements for Federal Civilian Executive Branch agencies. CISA says the directive requires agencies to prioritize rapid remediation of high-risk vulnerabilities, specifically KEV-listed Common Vulnerabilities and Exposures on publicly exposed assets that would grant total control of the asset after exploitation. Lower-risk vulnerabilities can be deferred under the directive’s risk-based framing.

The practical gap is still inventory. BOD 26-04 also sets basic expectations for when agencies must check whether threat actors compromised a system before a patch was applied. That makes the CISA alert more than a patch queue note for FCEB agencies with the affected products exposed. For everyone outside that boundary, CISA stops at encouragement: adopt risk-based vulnerability management and prioritize KEV Catalog vulnerabilities.


Published ·Deep Fathom