← Back to the dashboard

How we track exploited software flaws

What the dashboard shows, where the numbers come from, how current they are, and what they can’t tell you.

The short answer

Thousands of software flaws are disclosed every year, far more than anyone can patch at once. Only a small share is ever used in real attacks. Since November 2021 the US Cybersecurity and Infrastructure Security Agency (CISA) has kept a public list of the ones that are: the Known Exploited Vulnerabilities catalogue. This dashboard shows how fast that list grows, whose software is on it, what kinds of mistakes the flaws are, and how quickly US federal agencies must fix them.

How we know

The catalogue. CISA adds a flaw when three things are true: it has a CVE number, the public identifier for a disclosed flaw; there is reliable evidence that attackers have exploited it; and there is a clear fix or mitigation. Each entry gives the vendor and product, a short description, the type of weakness, the date added, a due date, and whether the flaw is known to have been used in ransomware campaigns. CISA publishes the whole catalogue as one file, under a CC0 licence that allows any use. We download it every night.

Our counts. Everything on the page is counted from that file: additions by month and year, the same period in earlier years, vendors, the most common weakness types (using the first type CISA lists for each flaw, with short names from MITRE’s Common Weakness Enumeration), and the age of each flaw when it was added, taken as the year added minus the year in its CVE number. The year in a CVE number is when the number was reserved, which is usually the year the flaw became known.

Deadlines. The due date binds US federal civilian agencies. Under Binding Operational Directive 22-01 of November 2021 the usual deadline for new entries was three weeks. Directive 26-04 of 10 June 2026 replaced it: deadlines now depend on whether a system is exposed to the internet, whether attacks can be automated and how much control they give, and the most urgent cases get three days and a forensic check for signs of compromise. In the data, 128 of the 164 entries added from 10 June to 13 November 2026 have a three-day deadline. We take each deadline as the due date minus the date added.

Our record. From 16 November 2026 we also keep every entry with the day we first saw it, the day CISA first marked it as used by ransomware, and any removal from the catalogue, so later versions of the page can show how long such marks take.

How current each part is

What the dashboard can’t tell you

How many attacks there were. The catalogue lists flaws that have been exploited at least once, not how often or against whom.

Every exploited flaw. Only flaws with a CVE number and a fix are listed, and CISA lists what it and its partners can confirm, which leans towards software used by the US government. A rising count can mean more attacks, or better detection and more reporting.

Which vendor is safest. Widely used software is attacked and studied more, so it appears more often. How quickly a vendor fixes flaws matters more than how many are found.

Whether your own systems are affected. For that, check the vendor’s advisory for each product you run.

Further reading

Credits

Data: CISA Known Exploited Vulnerabilities catalogue, distributed under the Creative Commons 0 1.0 licence. Weakness names, shortened, from the Common Weakness Enumeration (CWE), Copyright © 2006–2026, The MITRE Corporation, used under the CWE terms of use; CWE is a trademark of The MITRE Corporation. Neither CISA nor MITRE has endorsed this site. We only download and present the public data.

← Back to the dashboard