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 2025, Other
Confirmed exploited in 2025. Product class: Other (the site's classifier of CISA's product names). Clear these
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2025-24989 CISA KEV | Microsoft · Power Pages Microsoft Power Pages Improper Access Control VulnerabilityCISA remediation due for federal agencies: Mar 14, 2025 | Feb 21, 2025 | 2 days | High 8.2 | 2% |
| CVE-2024-49035 CISA KEV | Microsoft · Partner Center Microsoft Partner Center Improper Access Control VulnerabilityCISA remediation due for federal agencies: Mar 18, 2025 | Feb 25, 2025 | 91 days | High 8.7 | 1% |
| CVE-2010-3765 CISA KEV | Mozilla · Multiple Products Mozilla Multiple Products Remote Code Execution VulnerabilityCISA remediation due for federal agencies: Oct 27, 2025 | Oct 3, 2025 | 5,455 days | Critical 9.8 | 83% |
| CVE-2025-59374 CISA KEV | ASUS · Live Update ASUS Live Update Embedded Malicious Code VulnerabilityCISA remediation due for federal agencies: Jan 7, 2026 | Dec 17, 2025 | 1 day | Critical 9.3 | 1% |
| CVE-2025-20393 CISA KEV | Cisco · Multiple Products Cisco Multiple Products Improper Input Validation VulnerabilityCISA remediation due for federal agencies: Dec 24, 2025 | Dec 17, 2025 | Same day | Critical 10.0 | 32% |
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.