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 2024, Mobile
Confirmed exploited in 2024. Product class: Mobile (the site's classifier of CISA's product names). Clear these
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2024-44309 CISA KEV | Apple · Multiple Products Apple Multiple Products Cross-Site Scripting (XSS) VulnerabilityCISA remediation due for federal agencies: Dec 12, 2024 | Nov 21, 2024 | 2 days | Medium 6.3 | 23% |
| CVE-2024-44308 CISA KEV | Apple · Multiple Products Apple Multiple Products Code Execution VulnerabilityCISA remediation due for federal agencies: Dec 12, 2024 | Nov 21, 2024 | 2 days | High 8.8 | 10% |
| CVE-2024-43093 CISA KEV | Android · Framework Android Framework Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Nov 28, 2024 | Nov 7, 2024 | 6 days before publication | High 7.3 | 1% |
| CVE-2024-43047 CISA KEV | Qualcomm · Multiple Chipsets Qualcomm Multiple Chipsets Use-After-Free VulnerabilityCISA remediation due for federal agencies: Oct 29, 2024 | Oct 8, 2024 | 1 day | High 7.8 | 1% |
| CVE-2024-36971 CISA KEV | Android · Kernel Android Kernel Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Aug 28, 2024 | Aug 7, 2024 | 58 days | High 7.8 | 3% |
| CVE-2024-39891 CISA KEV | Twilio · Authy Twilio Authy Information Disclosure VulnerabilityCISA remediation due for federal agencies: Aug 13, 2024 | Jul 22, 2024 | 21 days | Medium 5.3 | 2% |
| CVE-2024-32896 CISA KEV | Android · Pixel Android Pixel Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Jul 4, 2024 | Jun 13, 2024 | Same day | High 8.1 | 3% |
| CVE-2024-4610 CISA KEV | Arm · Mali GPU Kernel Driver Arm Mali GPU Kernel Driver Use-After-Free VulnerabilityCISA remediation due for federal agencies: Jul 3, 2024 | Jun 12, 2024 | 5 days | High 7.4 | 1% |
| CVE-2024-29748 CISA KEV | Android · Pixel Android Pixel Privilege Escalation VulnerabilityCISA remediation due for federal agencies: Apr 25, 2024 | Apr 4, 2024 | 1 day before publication | High 7.8 | 1% |
| CVE-2024-29745 CISA KEV | Android · Pixel Android Pixel Information Disclosure VulnerabilityCISA remediation due for federal agencies: Apr 25, 2024 | Apr 4, 2024 | 1 day before publication | Medium 5.5 | 0% |
| CVE-2024-23296 CISA KEV | Apple · Multiple Products Apple Multiple Products Memory Corruption VulnerabilityCISA remediation due for federal agencies: Mar 27, 2024 | Mar 6, 2024 | 1 day | High 7.8 | 1% |
| CVE-2024-23225 CISA KEV | Apple · Multiple Products Apple Multiple Products Memory Corruption VulnerabilityCISA remediation due for federal agencies: Mar 27, 2024 | Mar 6, 2024 | 1 day | High 7.8 | 1% |
| CVE-2023-21237 CISA KEV | Android · Pixel Android Pixel Information Disclosure VulnerabilityCISA remediation due for federal agencies: Mar 26, 2024 | Mar 5, 2024 | 252 days | Medium 6.2 | 0% |
| CVE-2022-48618 CISA KEV | Apple · Multiple Products Apple Multiple Products Memory Corruption VulnerabilityCISA remediation due for federal agencies: Feb 21, 2024 | Jan 31, 2024 | 22 days | High 7.0 | 0% |
| CVE-2023-41974 CISA KEV | Apple · iOS and iPadOS Apple iOS and iPadOS Use-After-Free VulnerabilityCISA remediation due for federal agencies: Mar 26, 2026 | Jan 21, 2024 | 11 days | High 7.8 | 2% |
| CVE-2023-41990 CISA KEV | Apple · Multiple Products Apple Multiple Products Code Execution VulnerabilityCISA remediation due for federal agencies: Jan 29, 2024 | Jan 5, 2024 | 116 days | High 7.8 | 1% |
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.