CISA Adds Six Actively Exploited Vulnerabilities to KEV Catalog: What Your Security Team Must Do Now
Cisco, Barracuda, Microsoft, Google, and Openwave flaws are under active attack — here's your 30-day response playbook
Published 2026-11-10
# CISA Adds Six Actively Exploited Vulnerabilities to KEV Catalog: What Your Security Team Must Do Now
CISA has updated its Known Exploited Vulnerabilities (KEV) Catalog with six newly confirmed, actively exploited flaws spanning Cisco BroadWorks, Barracuda Networks, Openwave Messaging, Microsoft Office Outlook, and Google Chromium — triggering mandatory remediation timelines under Binding Operational Directive (BOD) 26-04 for federal agencies and raising the urgency bar for every regulated commercial organization.
What CISA's Advisory Actually Says
The six vulnerabilities added to the KEV Catalog cover a range of serious weakness classes:
- Cisco BroadWorks — an improper restriction of XML External Entity (XXE) references that could allow attackers to read sensitive server-side files or trigger server-side request forgery.
- Barracuda Networks (two entries) — an OS command injection flaw affecting multiple Barracuda products, plus an authentication bypass vulnerability specific to the Email Security Gateway (ESG) that lets attackers reach protected functionality through an alternate path.
- Openwave Messaging Webtop Media Transcoder — an incorrect resource transfer between security spheres, a class of flaw that can expose data or functionality across trust boundaries.
- Microsoft Office Outlook — a missing user-interaction guard for a potentially unsafe action, meaning an attacker may be able to trigger harmful behavior without requiring the user to explicitly approve it.
- Google Chromium — a use-after-free vulnerability in the browser engine, a memory-corruption class frequently leveraged for remote code execution or sandbox escape.
BOD 26-04 reinforces the KEV Catalog as the authoritative signal for patch prioritization across Federal Civilian Executive Branch (FCEB) agencies, with binding remediation deadlines that begin counting from the date of catalog addition.
Why This Matters Beyond the Federal Perimeter
While BOD 26-04 is a federal mandate, the KEV Catalog is widely recognized as the clearest public signal that a vulnerability is being weaponized at scale. Organizations subject to NIS2, SOC 2, ISO 27001, HIPAA, or PCI DSS all carry explicit obligations to respond to known, exploited threats in a timely, documented manner.
- NIS2 Article 21 requires essential and important entities to have vulnerability-handling and patch-management processes that reflect current threat intelligence — KEV additions are exactly the kind of authoritative signal regulators expect you to act on.
- ISO 27001 Annex A Control 8.8 (management of technical vulnerabilities) mandates timely identification and remediation based on risk — active exploitation is the highest-risk signal available.
- PCI DSS Requirement 6.3 ties patch timelines directly to exploit availability; KEV-listed vulnerabilities effectively reset the clock to the most aggressive remediation window.
- HIPAA Security Rule (45 CFR § 164.308) requires regular review of information system activity and risk analysis — unpatched KEV vulnerabilities in clinical or administrative environments are a material risk gap.
- SOC 2 CC7.1 evaluates whether security configurations and patch processes respond to new information — auditors increasingly reference KEV status as evidence of control effectiveness.
Your 7–30 Day Response Checklist
Within 7 days:
- Inventory all instances of Cisco BroadWorks, Barracuda ESG and affected products, Openwave Webtop Media Transcoder, Microsoft Outlook (all supported versions), and Google Chromium-based browsers across your environment.
- Confirm patch or vendor mitigation availability and open emergency change tickets.
- Isolate or restrict internet-facing instances of Barracuda ESG if patching cannot begin immediately — authentication bypass flaws on mail security gateways carry extreme exposure.
Within 14 days:
- Apply all available vendor patches and document remediation evidence tied to your compliance framework controls (NIS2, ISO 27001, PCI DSS, etc.).
- Run threat-hunt queries for indicators associated with XXE exploitation, command injection, and use-after-free memory anomalies across logs from the past 90 days.
- Update your risk register to reflect KEV status and evidence of active exploitation.
Within 30 days:
- Validate patch deployment through authenticated scanning and close all related tickets with evidence artifacts.
- Brief your CISO and compliance leads on control gaps surfaced during remediation — these are audit-ready findings, not just operational tasks.
- Review your vulnerability management SLAs against BOD 26-04 timelines even if you are not a federal agency; regulators in NIS2 jurisdictions are increasingly benchmarking commercial expectations against federal standards.
How RDS GoSOC AI Helps You Respond and Stay Compliant
RDS GoSOC AI maps threat intelligence — including KEV Catalog additions — across 27 compliance frameworks, so your security and compliance teams see the same risk picture at the same time. When a KEV alert lands, the platform surfaces the relevant control gaps across NIS2, SOC 2, ISO 27001, HIPAA, PCI DSS, and more, so you can prioritize remediation with audit evidence built in from day one.
Start a 14-day free trial at the RDS GoSOC AI platform — every paid feature is unlocked from minute one, and no credit card is required. Once you're inside, open the User Guide tab to orient your team, and reach out to Sage, the in-platform AI assistant, to walk through how the KEV alerts map to your specific framework obligations. Active exploitation doesn't wait for procurement cycles — your trial doesn't have to either.
---
#MSP #ManagedServices #CMMC #FedRamp #CyberSecurity #SOC #SecurityOperations #MSSP #ThreatDetection #Compliance #CloudSecurity #IdentitySecurity #SecurityMonitoring #ITServices #CyberResilience #ManagedSecurity #BusinessGrowth