Vendor History

Guides

What does it mean when your vendor is on CISA's KEV list?

Updated

CISA's Known Exploited Vulnerabilities (KEV) catalog is the US government's list of software flaws that attackers are known to be using. If a product you use has a flaw on the list, install the fix. A listing does not mean the vendor itself was hacked. In the 12 months to Oct 26, 2026, CISA added 190 flaws in products from 36 of the 112 vendors Vendor History tracks. Microsoft (42), Cisco (20) and Google (13) had the most.

How a flaw gets on the list

CISA, the US Cybersecurity and Infrastructure Security Agency, adds a flaw only when three things are true (CISA):

How a flaw gets on CISA's Known Exploited Vulnerabilities list. All three must be true: 1. The flaw has a CVE ID, a public tracking number. 2. There is reliable evidence attackers are using it. 3. There is a clear fix, such as an update from the vendor. Then CISA adds it to the list, with a required action like 'Apply updates per vendor instructions.' What you do: update the product, or stop using it if no fix is available.
  1. The flaw has a CVE ID, the public tracking number security flaws get.
  2. There is reliable evidence that attackers are actively using it.
  3. There is a clear way to fix it, such as an update from the vendor.

Each entry names the vendor and product, the date CISA added it and a required action. In CISA's catalog of Oct 23, 2026, the most common required action was "Apply updates per vendor instructions." Some entries add "or discontinue use of the product if mitigations are unavailable" (KEV catalog). CISA also marks whether a flaw is known to be used in ransomware campaigns.

What a listing means, and what it doesn't

A listing means attackers have used that flaw against real systems. If you run the product and haven't installed the fix, you're open to an attack that's already known to work.

It doesn't mean the vendor was breached or that your data was taken. That would show up as a breach notice or an SEC filing, which Vendor History tracks separately.

The counts aren't a safety ranking either. A company that makes lots of widely used products has more chances to show up. Read a high count as "you'll be installing a lot of updates," not as a grade for the company.

Which vendors had the most flaws added this year

This table is rebuilt from CISA's catalog every day. Each vendor links to its page, which lists every flaw with a link to its public record.

Flaws added to CISA's exploited list, Oct 27, 2025 to Oct 26, 2026. Top 15 of the vendors we track. Data checked Oct 26, 2026.
VendorLast 12 monthsOf those, CISA says used in ransomwareAll time (since Nov 2021)
Microsoft (Microsoft 365, Windows)424390
Cisco202101
Google (Workspace, Chrome, Android)13092
Fortinet12032
Apple10095
Adobe6082
Citrix6027
Ivanti6036
Oracle5146
SonicWall5219
Zimbra (Synacor)5019
Check Point415
SolarWinds4111
VMware (Broadcom)4134
Gladinet (CentreStack)304

See firewalls, VPNs and routers and IT management, remote access and backup for the kinds of products most small businesses install themselves.

Who has to act on the list

US federal civilian agencies must fix flaws on the list by set deadlines. That rule is now Binding Operational Directive 26-04, issued June 10, 2026, which replaced BOD 22-01 from Nov 3, 2021. Private businesses don't have to follow it, but CISA "strongly recommends all organizations review and monitor the KEV catalog" (CISA).

What a small business can do

  1. List the products you install and update yourself. Firewalls, VPNs, remote access tools, file transfer servers, email servers and phone systems. These are the products you have to keep updated yourself.
  2. Look up each vendor here. Search all vendors and open the flaws section on each page.
  3. Ask whoever runs your IT whether the fixes for those flaws are installed. If a product is too old to get updates, plan to replace it.
  4. Turn on automatic updates wherever the product offers them.

This is general information, not security advice for your setup. A flaw being on CISA's list doesn't tell you whether your copy of the product is affected. Check the vendor's notice for the versions involved.