CISA Adds Six Actively Exploited Flaws to KEV Catalog

Threat actors are currently chaining an authentication bypass with a command injection flaw to gain complete root access to Barracuda Email Security Gateway appliances. This urgent warning comes as the Cybersecurity and Infrastructure Security Agency (CISA) added six vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog on November 10, signaling a period of heightened activity from sophisticated threat groups. The update emphasizes that while numerical severity scores provide a baseline for risk, the reality of active exploitation demands immediate attention regardless of whether a bug is rated as critical or medium. These entries cover a diverse range of products, including Barracuda appliances, Cisco’s telecommunications infrastructure, legacy webmail components, and ubiquitous software like Microsoft Outlook and Google Chrome. The inclusion of these flaws indicates that attackers are effectively identifying and weaponizing gaps in enterprise defenses, often bypassing traditional security measures like multi-factor authentication through clever exploit chains.

The emergence of these threats necessitates a fundamental shift in how organizations manage their patch cycles, moving away from a slow, score-based triage toward a dynamic model informed by real-world threat intelligence. CISA’s catalog serves as the definitive source for this intelligence, stripping away the theoretical nature of vulnerability management and replacing it with actionable mandates. For federal agencies, the clock is already ticking to remediate these specific gaps, but the implications extend far beyond government networks. As third-party service providers and telecommunications giants find themselves in the crosshairs, the potential for downstream impact on private enterprises and individual users grows exponentially. By highlighting these six flaws, the agency is not just identifying software bugs; it is mapping out the current tactical preferences of global adversaries who are increasingly leveraging automation and specialized exploit kits to achieve their objectives.

1. Detailed Overview of Security Vulnerabilities That Have Been Recently Added to the Known Exploited Vulnerabilities Catalog

CISA’s latest expansion of the KEV catalog introduces six distinct CVEs that are currently being leveraged in the wild by a variety of threat actors. These vulnerabilities were identified through coordinated research and incident response efforts, revealing that attackers are not just targeting the newest software, but also successfully finding and exploiting older, unpatched systems. The catalog update is governed by Binding Operational Directive 26-04, which mandates that federal civilian executive branch agencies prioritize the remediation of these specific flaws. This directive is part of a broader strategy to reduce the national attack surface by focusing resources on the vulnerabilities that pose the most significant and immediate risk. While the directive is legally binding only for federal agencies, CISA strongly encourages private sector organizations to adopt the same timelines and prioritization logic to stay ahead of the evolving threat landscape.

The list of added vulnerabilities includes highly specific edge-case bugs and widely applicable zero-day flaws. Among them are two critical issues in Barracuda Email Security Gateway (ESG) appliances, an XML external entity reference flaw in Cisco BroadWorks, an incorrect resource transfer issue in Openwave Webtop Media Transcoder, a missing user interaction flaw in Microsoft Outlook, and a use-after-free bug in the Chromium engine. The diversity of these targets—ranging from specialized telecommunications hardware to everyday productivity tools—illustrates the breadth of modern attack campaigns. Each of these vulnerabilities was added because there is clear, documented evidence of malicious use, making them significantly more dangerous than thousands of other unexploited vulnerabilities with higher theoretical severity scores. This update serves as a reminder that the presence of a bug in the KEV catalog is the most reliable indicator that an organization should move to patch it immediately, often overriding internal schedules.

2. Barracuda ESG: Chaining Flaws for Root Access

The vulnerabilities affecting Barracuda Email Security Gateway (ESG) appliances represent the most severe and immediate threat within the current KEV update. By combining CVE-2026-116606, an authentication bypass, with CVE-2026-111560, a command injection flaw, attackers can achieve complete root access to affected devices. This chain is particularly dangerous because it allows an unauthenticated adversary to bypass standard security checks and execute arbitrary commands with the highest level of privilege. The process begins when an attacker sends a specially crafted request to the appliance’s administrative interface, exploiting the authentication bypass to gain a foothold. Once they have bypassed the initial gateway, they can leverage the command injection vulnerability to run malicious scripts, effectively taking full control over the email traffic and sensitive data passing through the system.

Technical analysis of this exploit chain reveals a significant failure in how input validation and session management were handled within the ESG architecture. The command injection component specifically targets the “timezone” field during a configuration import process; because this field was not properly sanitized, shell metacharacters could be inserted to trigger command execution. The combination of these two bugs removes the requirement for an attacker to possess valid administrative credentials, which is typically the most significant barrier to such an attack. Barracuda has confirmed that a small number of organizations have already been targeted by this specific chain, prompting an urgent call for all users of the ESG appliance to apply the necessary patches. Furthermore, because the command injection flaw exists in shared code, it also affects other Barracuda products, such as the Web Application Firewall and Message Archiver, although the full root-access chain may not be applicable to those specific environments.

3. Cisco BroadWorks: Targeting Telecom Infrastructure

Cisco BroadWorks, a widely used platform for telecommunications service providers, is currently being targeted through a vulnerability identified as CVE-2026-20320. This flaw involves an improper restriction of XML external entity (XXE) references, which an unauthenticated attacker can exploit to read sensitive configuration files and potentially other system data. By sending a malformed XML message to the platform’s provisioning interface, the attacker tricks the system into revealing internal information that should be strictly protected. This type of information disclosure is a critical precursor to more advanced attacks, as it provides an adversary with the blueprints of the network infrastructure, including credentials, billing details, and subscriber records. The scale of this threat is magnified by the fact that BroadWorks is central to the operations of many large-scale communication service providers globally.

Recent reports from security researchers indicate that a sophisticated, Chinese-speaking threat actor is actively exploiting this BroadWorks flaw as part of a broad campaign. This actor is allegedly using an autonomous, AI-driven intrusion harness to scan for vulnerable servers and automate the initial phases of the attack. At least 13 organizations, primarily located in Europe, have been identified as potential victims of this campaign, which appears to focus on asset enumeration and high-value data harvesting. The use of AI in this context signals a worrying trend where attackers can rapidly identify and exploit vulnerabilities at a speed that traditional manual defenses cannot match. Cisco has released patches for the affected products, including the Application Server and the Profile Server, and strongly advises service providers to limit access to their provisioning interfaces to mitigate the risk of exposure while updates are being scheduled.

4. Openwave Webtop: A Critical Legacy Technical Fix That Was Unfortunately Ignored by the Development Community

The inclusion of CVE-2026-111793 in the KEV catalog highlights a recurring problem in cybersecurity: the persistence of unpatched legacy software. This vulnerability affects the Openwave Webtop Media Transcoder, a component used by various telecommunications and email service providers. The flaw allows for an incorrect resource transfer between spheres, which can be exploited by an authenticated attacker to bypass file-type restrictions and gain access to sensitive information. What makes this case particularly notable is that the vendor released the fix for this vulnerability in late 2021. However, five years later, attackers are still finding and exploiting unpatched instances of this software. This demonstrates that even when patches are available, the complexity of upgrading service-provider-grade infrastructure often leads to dangerous delays in implementation.

Despite having a relatively low CVSS score of 4.3, the Openwave flaw has been prioritized by CISA due to its active exploitation by threat actors. This scenario serves as a powerful case study for why security teams cannot rely solely on numerical risk ratings. A “medium” severity bug in a critical piece of infrastructure, such as a webmail platform, can provide attackers with the exact foothold they need to conduct widespread data theft. In the current environment, attackers are increasingly looking for these overlooked gaps in legacy components, knowing that many organizations focus their attention only on the most recently discovered critical bugs. For service providers using Openwave technology, the remediation path involves moving to the latest supported Media Server releases and ensuring that the transcoder component is fully updated to the version released five years ago or a more recent iteration.

5. Outlook and Chromium: Rapid Exploitation

The software we use most frequently—browsers and email clients—remains a primary target for rapid exploitation, as evidenced by the new additions to the KEV catalog for Microsoft Outlook and Google Chromium. The Outlook vulnerability, CVE-2026-124194, was patched the same day it was added to the list, marking it as a true zero-day threat. This flaw is particularly insidious because it lacks a user interaction requirement for a potentially unsafe action. An attacker can send a specially crafted message that, when opened, triggers a connection to an external server controlled by the adversary. This connection can leak the user’s NTLMv2 hash, which can then be used for offline password cracking or relay attacks to gain further access to the corporate network. Because this happens without the usual “external content” warnings, even security-conscious users can be compromised simply by viewing an email.

Simultaneously, a use-after-free vulnerability in the Chromium engine, identified as CVE-2026-125350, has also been weaponized. This flaw affects not only Google Chrome but also other Chromium-based browsers, such as Microsoft Edge and Opera. Exploiting this bug allows a remote attacker to execute arbitrary code within the browser’s sandbox through a carefully crafted HTML page. While the sandbox is designed to prevent such code from affecting the underlying operating system, sandbox escapes are a common follow-up in sophisticated attack chains. A critical operational challenge with browser patches is that an update is often not fully applied until the application is restarted. Many users leave their browsers open for days or weeks, remaining vulnerable to exploitation even after the patch has been downloaded. Administrators must therefore ensure that their fleet management tools not only deploy the update but also enforce a browser restart to close the window of opportunity for attackers.

6. Federal Compliance and Deadlines

The inclusion of these six vulnerabilities in the KEV catalog triggers specific legal and operational requirements for federal civilian executive branch agencies under Binding Operational Directive 26-04. CISA has set staggered deadlines for these flaws based on the perceived risk and the availability of patches. The Barracuda ESG vulnerabilities carry the shortest deadline, with remediation required by November 13. This aggressive timeline reflects the critical nature of the root-access exploit and the immediate threat to government communications. Agencies are not only required to apply the patches but are also mandated to perform forensic triage to determine if their systems were compromised prior to the update. This step is crucial because a patch does not remove an attacker who has already established a persistent presence or created backdoors within the system.

The remaining four vulnerabilities—affecting Cisco, Openwave, Outlook, and Chromium—have a remediation deadline of November 24. This gives agencies slightly more time to coordinate updates across their distributed environments, though the urgency remains high. While these deadlines are mandatory for the federal government, they serve as a vital signal to the private sector about which threats require the most immediate intervention. By following the CISA timelines, private companies can align their security efforts with the most current understanding of global threat activity. The directive also highlights the importance of asset visibility; an organization cannot patch what it does not know it has. Therefore, a significant portion of the compliance effort involves performing thorough scans to identify every instance of the affected software, including legacy components and third-party tools that may be running vulnerable versions of Chromium or other shared libraries.

7. Addressing Critical Security Infrastructure Questions

One of the most pressing questions arising from the Barracuda ESG disclosure is whether multi-factor authentication (MFA) provides any protection against these attacks. Unfortunately, in the case of CVE-2026-116606, the answer is no. Because the vulnerability is an authentication bypass that occurs at the system level before the MFA challenge is even triggered, the presence of a second factor does not stop an attacker from reaching the administrative interface and proceeding with the exploit chain. This underscores a critical lesson in infrastructure security: MFA is an essential layer of defense for user accounts, but it is not a silver bullet against flaws in the underlying software architecture. The most effective mitigation in this instance is to ensure the administrative UI is not exposed to the public internet and is only accessible through secure, internal network segments.

Another common concern involves the adequacy of patching after a system has been exposed to active exploitation; for devices like the Barracuda ESG or Cisco BroadWorks servers, simply applying the latest security update may not be enough if an adversary has already gained root access. Security professionals must assume that an unpatched, internet-facing appliance that was targeted has been compromised. This means that after patching, a comprehensive review of the system’s configuration, outbound network logs, and account activities must be conducted. Organizations should look for unauthorized configuration imports, new administrative accounts, or unusual connections to external IP addresses. If evidence of a compromise is found, the only truly safe course of action may be to wipe the device and restore it from a known-good backup that predates the exploitation window, followed by immediate patching.

8. Developing a Resilient Security Posture

The recent updates to the CISA KEV catalog demonstrated how quickly the threat landscape shifted when attackers prioritized infrastructure targets. Organizations that moved aggressively to address the Barracuda and Cisco flaws found themselves in a much stronger position than those that waited for their scheduled maintenance windows. By adopting the KEV catalog as a primary driver for patch prioritization, these proactive teams moved away from the traditional, often ineffective strategy of only patching “critical” bugs and instead focused on the vulnerabilities that were actually being used in real-world attacks. This shift in mindset was essential for defending against adversaries who leveraged AI and automated scanning to find unpatched systems within minutes of a vulnerability becoming public.

Looking back at the deployment of these fixes, the most successful implementations were those that combined technical updates with rigorous forensic analysis. Security administrators verified that their systems remained uncompromised by reviewing logs and monitoring for anomalous behavior long after the patches were applied. This holistic approach ensured that even if a breach had occurred during the window of vulnerability, the threat was identified and mitigated before it could lead to catastrophic data loss. As the industry moved forward, the lessons learned from this batch of exploits informed a new standard for vulnerability management, where exposure, exploitability, and real-world intelligence were valued more highly than any static severity score. Organizations that embraced this dynamic model built a more resilient defense against the relentless evolution of modern cyber threats.

subscription-bg
Subscribe to Our Weekly News Digest

Stay up-to-date with the latest security news delivered weekly to your inbox.

Invalid Email Address
subscription-bg
Subscribe to Our Weekly News Digest

Stay up-to-date with the latest security news delivered weekly to your inbox.

Invalid Email Address