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, IoT and OT devices
Confirmed exploited in 2025. Product class: IoT and OT devices (the site's classifier of CISA's product names). Clear these
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2022-23748 CISA KEV | Audinate · Dante Discovery Dante Discovery Process Control VulnerabilityCISA remediation due for federal agencies: Feb 27, 2025 | Feb 6, 2025 | 813 days | High 7.8 | 8% |
| CVE-2024-41710 CISA KEV | Mitel · SIP Phones Mitel SIP Phones Argument Injection VulnerabilityCISA remediation due for federal agencies: Mar 5, 2025 | Feb 12, 2025 | 185 days | Medium 6.8 | 42% |
| CVE-2025-1316 CISA KEV | Edimax · IC-7100 IP Camera Edimax IC-7100 IP Camera OS Command Injection VulnerabilityCISA remediation due for federal agencies: Apr 9, 2025 | Mar 19, 2025 | 15 days | Critical 9.8 | 74% |
| CVE-2024-6047 CISA KEV | GeoVision · Multiple Devices GeoVision Devices OS Command Injection VulnerabilityCISA remediation due for federal agencies: May 28, 2025 | May 7, 2025 | 324 days | Critical 9.8 | 10% |
| CVE-2024-11120 CISA KEV | GeoVision · Multiple Devices GeoVision Devices OS Command Injection VulnerabilityCISA remediation due for federal agencies: May 28, 2025 | May 7, 2025 | 174 days | Critical 9.8 | 28% |
| CVE-2023-38950 CISA KEV | ZKTeco · BioTime ZKTeco BioTime Path Traversal VulnerabilityCISA remediation due for federal agencies: Jun 9, 2025 | May 19, 2025 | 656 days | High 7.5 | 92% |
| CVE-2025-4632 CISA KEV | Samsung · MagicINFO 9 Server Samsung MagicINFO 9 Server Path Traversal VulnerabilityCISA remediation due for federal agencies: Jun 12, 2025 | May 22, 2025 | 9 days | Critical 9.8 | 24% |
| CVE-2020-25079 CISA KEV | D-Link · DCS-2530L and DCS-2670L Devices D-Link DCS-2530L and DCS-2670L Command Injection VulnerabilityCISA remediation due for federal agencies: Aug 26, 2025 | Aug 4, 2025 | 1,797 days | High 8.8 | 54% |
| CVE-2020-25078 CISA KEV | D-Link · DCS-2530L and DCS-2670L Devices D-Link DCS-2530L and DCS-2670L Devices Unspecified VulnerabilityCISA remediation due for federal agencies: Aug 26, 2025 | Aug 4, 2025 | 1,797 days | High 7.5 | 98% |
| CVE-2025-57819 CISA KEV | Sangoma · FreePBX Sangoma FreePBX Authentication Bypass VulnerabilityCISA remediation due for federal agencies: Sep 19, 2025 | Aug 28, 2025 | Same day | Critical 10.0 | 95% |
| CVE-2025-4008 CISA KEV | Smartbedded · Meteobridge Smartbedded Meteobridge Command Injection VulnerabilityCISA remediation due for federal agencies: Oct 23, 2025 | Oct 1, 2025 | 133 days | High 8.7 | 93% |
| CVE-2021-26829 CISA KEV | OpenPLC · ScadaBR OpenPLC ScadaBR Cross-site Scripting VulnerabilityCISA remediation due for federal agencies: Dec 19, 2025 | Nov 28, 2025 | 1,631 days | Medium 5.4 | 48% |
| CVE-2021-26828 CISA KEV | OpenPLC · ScadaBR OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type VulnerabilityCISA remediation due for federal agencies: Dec 24, 2025 | Dec 2, 2025 | 1,635 days | High 8.8 | 39% |
| CVE-2023-52163 CISA KEV | Digiever · DS-2105 Pro Digiever DS-2105 Pro Missing Authorization VulnerabilityCISA remediation due for federal agencies: Jan 12, 2026 | Dec 22, 2025 | 323 days | High 8.8 | 97% |
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.