CISA put six more vulnerabilities into its Known Exploited Vulnerabilities (KEV) catalog on 10 November, citing evidence of active exploitation. Two of them are Barracuda appliance bugs that the catalog describes as chainable, and both carry the shortest deadline of the batch: 13 November for federal civilian agencies, three days after listing. The other four, in Cisco BroadWorks, an Openwave media transcoder, Microsoft Outlook and Chromium, have until 24 November. Organisations outside the federal government face the same exposure without the formal deadline.
Start with the Barracuda pair
The two Barracuda entries are the ones to act on first, for three reasons: the deadline, the instruction to look for earlier compromise, and the way they fit together.
- CVE-2026-116606 affects the Email Security Gateway. CISA classes it as an authentication bypass through an alternate path. Per the catalog, an unauthenticated attacker can use the configuration-import function to restore a crafted backup and rewrite the appliance’s global configuration.
- CVE-2026-111560 is an operating-system command injection that the catalog lists against multiple Barracuda products, naming seven products, among them the Email Security Gateway, Load Balancer, ADC, Web Application Firewall and Web Security Gateway. It requires an administrator, and a crafted timezone value leads to commands running as root.
On their own, the first needs no login but only changes configuration, and the second hands over root but needs administrator access. The catalog notes each as chainable with the other. That is the dangerous reading: a flaw that removes the need for credentials, paired with one that converts administrator-level reach into full control of the box. CISA does not say how attackers are combining them, or whether they are, only that exploitation of each is evidenced.
Both entries are marked as requiring forensic triage. Under Binding Operational Directive 26-04, which replaced the older BOD 22-01, agencies are expected to establish whether an intruder was already present before the fix went on, not merely to patch. CISA’s implementation guidance suggests scoping within hours of a listing, preserving volatile evidence before remediating, and finishing triage analysis within roughly two days.
The other four
Cisco BroadWorks (CVE-2026-20320) is an XML external entity flaw. CISA’s summary says an unauthenticated remote attacker could read sensitive configuration information. Cisco has a security advisory, and the due date is 24 November.
Openwave Webtop Media Transcoder (CVE-2026-111793) is classed as an incorrect resource transfer between spheres. According to the catalog, an authenticated user who bypasses the webmail interface could get the transcoder to process and convert document types that should be out of reach. The entry points to a GitHub advisory and a Japanese coordination centre notice. It is a narrower product than the others here, which makes it easy to overlook in an inventory of webmail-adjacent components.
Microsoft Outlook (CVE-2026-124194) is a missing-user-interaction flaw for a potentially unsafe action, categorised as spoofing. CISA says an unauthorised attacker could carry it out over the network. The catalog gives no further detail on what is spoofed or what the victim sees, and Microsoft’s update guide is the place to confirm which builds are affected.
Chromium (CVE-2026-125350) is a use-after-free. A remote attacker could run arbitrary code inside the browser sandbox through a crafted web page. CISA’s entry says other Chromium-based browsers, such as Microsoft Edge and Opera, are affected too. The catalog points to Google’s stable-channel post of 9 November for this entry; that post does not itself describe the flaw or its exploitation. Code execution inside the sandbox is not the same as escaping it; an attacker normally needs a second bug for that, and nothing public says whether one is in use here.
What is confirmed and what is not
CISA’s statement is that it added all six on evidence of active exploitation. The catalog lists known ransomware use as “Unknown” for every entry. Nothing published by the agency names the attackers, the sectors hit, the number of victims, or when exploitation began. CISA’s entries do not say how, or whether, the two Barracuda bugs were joined in a single intrusion.
What to do, in order
- Barracuda first. Apply the vendor’s fixes or mitigations to every affected appliance, starting with anything reachable from the internet, before 13 November if you follow the federal timeline. Treat the management interface as something that should never face the public network.
- Check before and after patching. On those appliances, review configuration history for imports or restores you did not initiate, look for unexpected administrator accounts or changed settings, and preserve logs before rebuilding. A patched device can still carry a configuration an attacker planted earlier.
- Update Chromium-based browsers everywhere. Browser updates are easy to leave to auto-update and forget. Confirm that managed fleets have actually restarted onto the fixed build, and include Edge and other derivatives, not just Chrome.
- Apply the Microsoft and Cisco fixes by 24 November, using each vendor’s advisory to identify affected versions.
- Inventory the quiet ones. Openwave components and Barracuda products other than the mail gateway are the likeliest to be missing from an asset list.
CISA also encourages organisations outside the federal government to treat KEV as a priority list for remediation, which is a sensible default for any team that cannot patch everything at once.
Frequently Asked Questions
Are the Barracuda vulnerabilities CVE-2026-116606 and CVE-2026-111560 being exploited? Yes. CISA added both to its Known Exploited Vulnerabilities catalog on 10 November on evidence of active exploitation, and notes them as chainable with each other. It has not said who is exploiting them or how widely.
When do the Barracuda KEV fixes have to be applied? Federal civilian agencies must act by 13 November, three days after listing, and both entries call for forensic triage. Other organisations should treat that date as their own target.
Does the Chromium flaw CVE-2026-125350 affect browsers other than Chrome? Yes. CISA’s entry says Chromium-based browsers such as Edge and Opera are affected too. Update each one to the vendor’s fixed release.
What is the deadline for the other four KEV additions? The Cisco BroadWorks, Openwave, Microsoft Outlook and Chromium entries are due on 24 November for federal civilian agencies.
Source: Cybersecurity and Infrastructure Security Agency (CISA).