CISA put six new flaws on its list of bugs that attackers are already using. CISA said on Nov. 10 that it had evidence of active exploitation for each one.
The new entries include Barracuda email security and other Barracuda products, Cisco BroadWorks, Openwave Webtop Media Transcoder, Microsoft Outlook and the Chromium engine used by several web browsers. Two Barracuda flaws carry the shortest federal deadline, Nov. 13, while the other four are due Nov. 24.
Key facts
- CISA added six flaws to its Known Exploited Vulnerabilities (KEV) Catalog, citing active exploitation.
- The list covers Cisco BroadWorks, two Barracuda entries, Openwave Webtop Media Transcoder, Microsoft Outlook and Google Chromium.
- The catalog feed sets a Nov. 13 due date for CVE-2026-111560 and CVE-2026-116606, both tied to Barracuda.
- The other four flaws have a Nov. 24 due date in the same feed.
- Known ransomware use is marked Unknown for all six entries.
Background
The KEV Catalog is the CISA list of flaws with proof of real-world attacks. In its alert, CISA said that bugs like these are a common way in for attackers and pose significant risks to the federal enterprise.
The deadlines come from Binding Operational Directive 26-04. According to CISA, BOD 26-04 tells FCEB agencies to fix high-risk KEV flaws on publicly exposed systems first, especially ones that hand an attacker total control. Lower-risk flaws can wait under that same directive, CISA said.
The directive also sets basic expectations for when agencies must look for signs that attackers got in before a patch went on. The BOD 26-04 text asks agencies to weigh four things: whether an asset faces the public internet, whether its flaw is in the KEV Catalog, whether an attacker can automate all exploit steps, and whether an attacker would gain partial or total control.
Here is what the catalog says about each new entry:
- Barracuda ESG, CVE-2026-116606: The catalog calls this an authentication bypass that could let a remote attacker with no login trigger a configuration-import feature and restore a crafted backup.
- Barracuda products, CVE-2026-111560: This is an OS command injection in several Barracuda products, ESG among them, that could let a signed-in administrator run commands as root.
- Cisco BroadWorks, CVE-2026-20320: A remote attacker without credentials could read sensitive configuration details, the catalog says.
- Microsoft Outlook, CVE-2026-124194: An unauthorized attacker could carry out spoofing over a network.
- Google Chromium, CVE-2026-125350: The catalog lists a use-after-free bug in the XML component that a crafted webpage could use to run code inside the browser sandbox.
- Openwave Webtop Media Transcoder, CVE-2026-111793: This flaw is part of the same batch, with a Nov. 24 due date.
The two Barracuda flaws matter together. The catalog says CVE-2026-116606 can be chained with CVE-2026-111560, so a login bypass and a root-level command flaw can be combined.
What it means for you
The deadlines bind only federal civilian agencies. Even so, CISA urges every organization to use risk-based vulnerability management and to put KEV flaws near the top of the fix list.
The catalog says the Chromium bug could affect browsers built on Chromium, including Google Chrome, Microsoft Edge and Opera.
The Outlook entry, the catalog says, could let an unauthorized attacker carry out spoofing over a network. Staff who know what to do after a suspicious message can find a starting point in what happens after an employee clicks a bad link.
Firms that run affected Barracuda products, including the Email Security Gateway, face the earliest federal deadline, Nov. 13. The catalog says the two Barracuda flaws can be chained, and one of them needs no login to start.
CISA does not estimate how many small businesses run any of these products. It also does not list patch version numbers on these pages; those live in vendor advisories.
Practical steps
The catalog gives the same required action for all six entries. Per the feed, organizations should apply vendor mitigations under BOD 26-04 and its Forensics Triage Requirements, follow BOD 26-04 cloud guidance or stop using a product if no mitigation exists, and check each asset's internet exposure.
A simple plan for a smaller team:
- Find the products. List every device and app that matches the six entries, starting with email gateways and browsers.
- Patch the Barracuda gear first. The federal due date for both Barracuda flaws is Nov. 13. Check the vendor's own advisory for the fix.
- Update browsers and Outlook. These carry a Nov. 24 due date for federal civilian agencies. Other organizations can apply vendor updates as they become available.
- Check exposure. Note which systems face the public internet, since the BOD 26-04 text treats public exposure as a key risk factor.
- Look for signs of a break-in. Patching does not undo access an attacker may already have, which is why the directive sets expectations for compromise checks.
- Shut it off if needed. If a fix is not available, the catalog says to discontinue use of the product.
Teams without spare time for this can get help. Our cybersecurity services can track urgent flaws and handle patching. A tested plan for disaster recovery and business continuity helps if an attack gets through anyway. For hosted email and servers, our cloud and infrastructure support can review what faces the internet.
What happens next
Federal agencies must meet the Nov. 13 and Nov. 24 deadlines set in the catalog. CISA keeps adding flaws to the list as it finds proof of attacks, so the catalog is worth checking often. An earlier post on another login bypass that joined the list shows how often this happens.
It is still not known whether any of the six has been used in a confirmed ransomware campaign. The catalog marks that field as Unknown for every entry.
Updated Nov 12, 2026: Passage 1 corrected from three to four BOD 26-04 variables, adding Exploit Automation; passage 2 fixed a missing word before the colon.



