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 May 2024
Confirmed exploited in May 2024. Clear these
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2024-1086 CISA KEV Ransomware | Linux · Kernel Linux Kernel Use-After-Free VulnerabilityCISA remediation due for federal agencies: Jun 20, 2024 | May 30, 2024 | 120 days | High 7.8 | 28% |
| CVE-2024-4978 CISA KEV | Justice AV Solutions · Viewer Justice AV Solutions (JAVS) Viewer Installer Embedded Malicious Code VulnerabilityCISA remediation due for federal agencies: Jun 19, 2024 | May 29, 2024 | 7 days | High 8.4 | 27% |
| CVE-2024-24919 CISA KEV Ransomware | Check Point · Quantum Security Gateways Check Point Quantum Security Gateways Information Disclosure VulnerabilityCISA remediation due for federal agencies: Jun 20, 2024 | May 29, 2024 | 1 day | High 8.6 | 100% |
| CVE-2024-5274 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Jun 18, 2024 | May 28, 2024 | Same day | High 8.3 | 7% |
| CVE-2020-17519 CISA KEV | Apache · Flink Apache Flink Improper Access Control VulnerabilityCISA remediation due for federal agencies: Jun 13, 2024 | May 23, 2024 | 1,234 days | Critical 9.1 | 98% |
| CVE-2024-4947 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Jun 10, 2024 | May 20, 2024 | 5 days | Critical 9.6 | 15% |
| CVE-2023-43208 CISA KEV Ransomware Health IT | NextGen Healthcare · Mirth Connect NextGen Healthcare Mirth Connect Deserialization of Untrusted Data VulnerabilityCISA remediation due for federal agencies: Jun 10, 2024 | May 20, 2024 | 208 days | Critical 9.8 | 83% |
| CVE-2024-4761 CISA KEV | Google · Chromium V8 Google Chromium V8 Out-of-Bounds Memory Write VulnerabilityCISA remediation due for federal agencies: Jun 6, 2024 | May 16, 2024 | 3 days | High 8.3 | 11% |
| CVE-2021-40655 CISA KEV | D-Link · DIR-605 Router D-Link DIR-605 Router Information Disclosure VulnerabilityCISA remediation due for federal agencies: Jun 6, 2024 | May 16, 2024 | 965 days | High 7.5 | 87% |
| CVE-2014-100005 CISA KEV | D-Link · DIR-600 Router D-Link DIR-600 Router Cross-Site Request Forgery (CSRF) VulnerabilityCISA remediation due for federal agencies: Jun 6, 2024 | May 16, 2024 | 3,411 days | High 8.0 | 43% |
| CVE-2024-30051 CISA KEV Ransomware | Microsoft · DWM Core Library Microsoft DWM Core Library Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Jun 4, 2024 | May 14, 2024 | Same day | High 7.8 | 6% |
| CVE-2024-30040 CISA KEV | Microsoft · Windows Microsoft Windows MSHTML Platform Security Feature Bypass VulnerabilityCISA remediation due for federal agencies: Jun 4, 2024 | May 14, 2024 | Same day | High 8.8 | 4% |
| CVE-2024-4671 CISA KEV | Google · Chromium Google Chromium Visuals Use-After-Free VulnerabilityCISA remediation due for federal agencies: Jun 3, 2024 | May 13, 2024 | 4 days | Critical 9.6 | 8% |
| CVE-2023-7028 CISA KEV | GitLab · GitLab CE/EE GitLab Community and Enterprise Editions Improper Access Control VulnerabilityCISA remediation due for federal agencies: May 22, 2024 | May 1, 2024 | 110 days | Critical 10.0 | 94% |
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.