Exploited now
Every vulnerability CISA confirms is being exploited in the wild: listed in its Known Exploited Vulnerabilities catalog, or assessed as actively exploited in its Vulnrichment data, often days before the catalog. When it was confirmed, how soon after the CVE went public, and the vendors attackers go after first. Refreshed every ten minutes. Sources.
Updated under an hour ago ()
What this means for you
28 vulnerabilities confirmed exploited in the last 30 days; 38% of the last 12 months' were exploited by the day they were disclosed. Add your stack to see which of them you run.
- Confirmed exploited, last 30 days
- 28
- Show in the list
- Exploited by the day of disclosure, last 12 months
- 38%
- of 295 confirmed
- Show in the list
- Median days from disclosure to confirmed exploitation
- 4
- last 12 months; list sorted fastest first
- Show in the list
- Used in ransomware campaigns, last 12 months
- 25
- Show in the list
What this means for a patch cycle
Half of the vulnerabilities CISA confirmed exploited in the last 12 months were confirmed within 4 days of going public, and 38% by the day they were published. A monthly patch cycle leaves those exposed for weeks. Products from the vendors below, especially internet-facing ones, need an emergency patch path measured in days.
Where attackers strike first
Vendors by vulnerabilities confirmed exploited in the last 24 months; the top five account for 67% of the twelve listed. This counts confirmed attacks, not disclosed flaws, so a vendor is not rewarded for publishing fewer CVEs. Mapped health IT products account for 1 of them.
Are any of these in your stack?
Name the products you run and see every CVE that affects them, with exploited ones first. Free for one product; subscribers add their whole inventory and are emailed the moment one is exploited.
Every confirmed exploitation
Showing: confirmed in 2022, Operating systems
Confirmed exploited in 2022. Product class: Operating systems (the site's classifier of CISA's product names). Clear these
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2004-0210 CISA KEV | Microsoft · Windows Microsoft Windows Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Mar 24, 2022 | Mar 3, 2022 | 6,441 days | High 7.8 | 7% |
| CVE-2002-0367 CISA KEV | Microsoft · Windows Microsoft Windows Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Mar 24, 2022 | Mar 3, 2022 | 6,910 days | High 7.8 | 5% |
| CVE-2015-1701 CISA KEV Ransomware | Microsoft · Win32k Microsoft Win32k Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Mar 24, 2022 | Mar 1, 2022 | 2,506 days | High 7.8 | 56% |
| CVE-2014-6352 CISA KEV | Microsoft · Windows Microsoft Windows Code Injection VulnerabilityCISA remediation due for federal agencies: Aug 25, 2022 | Feb 25, 2022 | 2,683 days | High 7.8 | 77% |
| CVE-2013-3906 CISA KEV | Microsoft · Graphics Component Microsoft Graphics Component Memory Corruption VulnerabilityCISA remediation due for federal agencies: Aug 15, 2022 | Feb 15, 2022 | 3,023 days | High 7.8 | 85% |
| CVE-2018-8174 CISA KEV Ransomware | Microsoft · Windows Microsoft Windows VBScript Engine Out-of-Bounds Write VulnerabilityCISA remediation due for federal agencies: Aug 15, 2022 | Feb 13, 2022 | 1,376 days | High 7.5 | 88% |
| CVE-2021-36934 CISA KEV | Microsoft · Windows Microsoft Windows SAM Local Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Feb 24, 2022 | Feb 10, 2022 | 203 days | High 7.8 | 67% |
| CVE-2020-0796 CISA KEV Ransomware | Microsoft · SMBv3 Microsoft SMBv3 Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 700 days | Critical 10.0 | 100% |
| CVE-2017-8464 CISA KEV | Microsoft · Windows Microsoft Windows Shell (.lnk) Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 1,702 days | High 8.8 | 90% |
| CVE-2017-0263 CISA KEV | Microsoft · Win32k Microsoft Win32k Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 1,735 days | High 7.8 | 10% |
| CVE-2015-1635 CISA KEV | Microsoft · HTTP.sys Microsoft HTTP.sys Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 2,494 days | Critical 9.8 | 100% |
| CVE-2015-1130 CISA KEV | Apple · OS X Apple OS X Authentication Bypass VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 2,498 days | High 7.8 | 10% |
| CVE-2014-4404 CISA KEV | Apple · OS X Apple OS X Heap-Based Buffer Overflow VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 10, 2022 | 2,702 days | High 7.8 | 49% |
| CVE-2017-0145 CISA KEV Ransomware Health IT | Microsoft · SMBv1 Microsoft SMBv1 Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 6, 2022 | 1,788 days | High 8.8 | 90% |
| CVE-2017-0144 CISA KEV Ransomware Health IT | Microsoft · SMBv1 Microsoft SMBv1 Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 10, 2022 | Feb 6, 2022 | 1,788 days | High 8.8 | 99% |
| CVE-2014-7169 CISA KEV | GNU · Bourne-Again Shell (Bash) GNU Bourne-Again Shell (Bash) Arbitrary Code Execution VulnerabilityCISA remediation due for federal agencies: Jul 28, 2022 | Jan 28, 2022 | 2,683 days | Critical 9.8 | 100% |
| CVE-2014-6271 CISA KEV | GNU · Bourne-Again Shell (Bash) GNU Bourne-Again Shell (Bash) Arbitrary Code Execution VulnerabilityCISA remediation due for federal agencies: Jul 28, 2022 | Jan 28, 2022 | 2,683 days | Critical 9.8 | 100% |
| CVE-2018-8453 CISA KEV Ransomware | Microsoft · Win32k Microsoft Win32k Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Jul 21, 2022 | Jan 19, 2022 | 1,197 days | High 7.8 | 70% |
| CVE-2013-3900 CISA KEV | Microsoft · WinVerifyTrust function Microsoft WinVerifyTrust function Remote Code ExecutionCISA remediation due for federal agencies: Jul 10, 2022 | Jan 10, 2022 | 2,953 days | Medium 5.5 | 45% |
| CVE-2022-21882 CISA KEV Ransomware | Microsoft · Win32k Microsoft Win32k Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Feb 18, 2022 | Jan 9, 2022 | 2 days before publication | High 7.0 | 59% |
| CVE-2019-1458 CISA KEV Ransomware | Microsoft · Win32k Microsoft Win32k Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Jul 10, 2022 | Jan 3, 2022 | 755 days | High 7.8 | 74% |
How to read this
"Confirmed exploited" is the date CISA added the CVE to its Known Exploited Vulnerabilities catalog or assessed it as actively exploited, whichever came first. It is when exploitation was confirmed publicly, not when attackers started, so "after publication" is an upper bound: attackers were there at least that soon. "By disclosure day" means confirmed on or before the day the CVE record was published, the closest public measure of a zero-day. Dates are US Eastern, the calendar CISA uses. Vendors are named as CISA's catalog names them, otherwise as the assigning CNA does. EPSS is FIRST's estimate of the chance of exploitation in the next 30 days.