Junious Media NetworkSaturday, November 21, 2026
Juni/Tech
Advertisement
Security

CISA Adds Eight Exploited Vulnerabilities in Two Days

Federal cyber officials added eight confirmed-exploit flaws to their public watch list in two days, urging every organization to patch high-risk systems without delay.

Key points

  1. CISA added four actively exploited vulnerabilities to its catalog on November 20, following four more additions on November 18.
  2. Binding Operational Directive 26-04 requires federal civilian agencies to prioritize patching catalog flaws on publicly exposed systems that could grant an attacker full control.
  3. The directive requires agencies to check for signs of compromise before applying any patch, to preserve forensic evidence.
  4. CISA encourages all organizations, not just federal agencies, to treat KEV catalog entries as urgent patching priorities.

The Cybersecurity and Infrastructure Security Agency added four actively exploited security flaws to its catalog on November 20, with each one confirmed under real-world attack. Two days earlier, the agency posted four more entries on November 18 under the same evidence standard.

The two rounds together placed eight new flaws on the federal government's public watch list. All eight carried confirmed exploitation evidence. That means attackers were already using them against real systems, not just testing them in a lab.

What the Known Exploited Vulnerabilities Catalog Does

CISA runs the KEV catalog as a free, searchable list of software and hardware flaws. Every entry has one thing in common: attackers have already used it in real attacks. The agency updates the list on a rolling basis as new exploitation evidence comes in.

IT teams often face thousands of disclosed flaws at once. The catalog cuts through that pile by pointing to the ones most likely in active use. That makes it a direct guide for where to focus patching work first.

The catalog spans products from many vendors, across a wide range of software and hardware types. Its value is not just the list of flaws, but the confirmed evidence behind each one. Every entry must meet three conditions before it is added.

Three Requirements for Every Catalog Entry

A flaw must have a CVE ID before it can be added. That is the standard identifier assigned to known security issues. It must also have documented proof that attackers are actively using it right now.

Advertisement

The third requirement is clear fix guidance. The flaw must have a known patch or a workaround before CISA will list it. That way, every catalog entry comes with a path to reducing the risk.

CISA also accepts submissions from the broader security community. Anyone can nominate a flaw through the agency's nomination form, as long as all three conditions are met. The goal is to keep the list current as new threats emerge.

How a Federal Directive Shapes the Patching Rules

The November additions fall under Binding Operational Directive 26-04. It is titled Prioritizing Security Updates Based on Risk. This directive sets patching rules for Federal Civilian Executive Branch agencies. Those are the departments and offices that form most of the non-military federal government.

Advertisement

The directive tells agencies to move fastest on a specific group of flaws. These are catalog entries found on systems open to the public internet. The focus lands on flaws that could hand an attacker full control of a system once used.

Lower-risk flaws can wait. Agencies can address those on a longer schedule. This lets limited IT staff put their energy where the danger is greatest.

Why Checking for a Breach Before Patching Matters

The directive adds one formal step before any patch goes in. Agencies must look for signs of a breach before applying a fix. If attackers already got in through a flaw, patching without looking first can cover their tracks.

Log reviews, endpoint alerts, and network traffic records can reveal unauthorized access. Finding a breach before patching keeps the forensic record intact. It also stops the patch from hiding what an attacker already did.

Advertisement

This check is now a required step, not just a suggestion. It applies each time a catalog flaw is patched on a system that could have been exposed.

Why Actively Exploited Vulnerabilities Demand a Faster Response

CISA has identified this category of flaw as a common path that bad actors use to reach government networks. The concern is not simply that a flaw was found and published. It is that someone already built a working exploit and is using it now.

When a flaw is confirmed exploited, the defense window shrinks fast. A newly disclosed flaw with no known exploit gives teams time to plan. A flaw already in active use could hit any unpatched system at any moment.

Federal networks carry sensitive data across health programs, law enforcement, finance, and security functions. A single successful exploit on a public-facing system could give an attacker full control of that asset. The catalog helps agencies flag those worst-case risks first.

What This Means for Organizations Outside the Federal Government

The directive only covers federal civilian agencies. Private companies, hospitals, schools, and state and local governments are not legally required to follow it. Even so, CISA urges every organization to treat catalog entries as urgent patching targets.

Advertisement

Many of the flaws that hit government networks exist in the same commercial software that businesses and utilities run. Automated tools let attackers scan the open internet for unpatched systems at scale. Sector does not matter to those scans.

Risk-based vulnerability management, the approach the directive formalizes for federal agencies, is a recognized best practice for any IT team. The catalog makes that approach simple. Each entry already carries real exploitation evidence, removing the guesswork about which flaws to fix first.

Advertisement

Steps Security Teams Should Take Now

When new entries appear, the first task is to confirm whether the affected product exists in your environment. Asset inventories and vulnerability scanners can answer that quickly. If the product is present and unpatched, it belongs at the top of the fix list.

Before applying any patch, run the same pre-patch check the directive requires of federal agencies. Look for signs of compromise in logs, endpoint alerts, and network records. Fixing a system without checking first may hide a breach that is already underway.

After confirming no active intrusion, or after containing one that is found, apply the patch or the vendor's recommended fix. CISA requires clear mitigation guidance before adding any flaw to the catalog. That guidance is already in place for every current entry.

What to Watch as the Catalog Keeps Growing

CISA said it will keep adding vulnerabilities as confirmed exploitation evidence arrives. The catalog can grow on any day. The November additions show how fast that can happen, with two separate rounds published in the same week.

Organizations can follow the catalog directly on the CISA website, where it is free to search and download. Many security platforms pull from it automatically, flagging new entries that match the systems they monitor.

The steady flow of new entries is a reminder that attackers keep finding value in known, unpatched flaws. Reviewing the catalog regularly is one of the most direct ways to track the specific bugs most likely to be turned against any organization.

Advertisement

Sources