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: last 24 months, Google
Showing Google only. Show every vendor
| CVE | Vendor and vulnerability | Confirmed exploited | After publication | Severity | EPSS |
|---|---|---|---|---|---|
| CVE-2026-58704 CISA KEV | Google · Pixel Google Pixel Improper Authorization VulnerabilityCISA remediation due for federal agencies: Sep 19, 2026 | Sep 16, 2026 | 1 day | High 8.8 | 1% |
| CVE-2026-87491 CISA KEV | Google · Chromium V8 Google Chromium V8 Out of Bounds Write VulnerabilityCISA remediation due for federal agencies: Sep 23, 2026 | Sep 9, 2026 | 1 day | High 8.8 | 3% |
| CVE-2026-85046 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Sep 18, 2026 | Sep 4, 2026 | 1 day | High 8.8 | 49% |
| CVE-2026-11645 CISA KEV | Google · Chromium V8 Google Chromium V8 Out-of-Bounds Read and Write VulnerabilityCISA remediation due for federal agencies: Jun 23, 2026 | Jun 7, 2026 | 1 day before publication | High 8.8 | 2% |
| CVE-2026-5281 CISA KEV | Google · Dawn Google Dawn Use-After-Free VulnerabilityCISA remediation due for federal agencies: Apr 15, 2026 | Mar 31, 2026 | 1 day before publication | High 8.8 | 1% |
| CVE-2026-3910 CISA KEV | Google · Chromium V8 Google Chromium V8 Improper Restriction of Operations Within the Bounds of a Memory Buffer VulnerabilityCISA remediation due for federal agencies: Mar 27, 2026 | Mar 12, 2026 | Same day | High 8.8 | 1% |
| CVE-2026-3909 CISA KEV | Google · Skia Google Skia Out-of-Bounds Write VulnerabilityCISA remediation due for federal agencies: Mar 27, 2026 | Mar 12, 2026 | Same day | High 8.8 | 2% |
| CVE-2026-2441 CISA KEV | Google · Chromium Google Chromium CSS Use-After-Free VulnerabilityCISA remediation due for federal agencies: Mar 10, 2026 | Feb 17, 2026 | 4 days | High 8.8 | 55% |
| CVE-2025-14174 CISA KEV | Google · Chromium Google Chromium Out of Bounds Memory Access VulnerabilityCISA remediation due for federal agencies: Jan 2, 2026 | Dec 12, 2025 | Same day | High 8.8 | 22% |
| CVE-2025-13223 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Dec 10, 2025 | Nov 19, 2025 | 2 days | High 8.8 | 5% |
| CVE-2025-10585 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Oct 14, 2025 | Sep 23, 2025 | 1 day before publication | High 8.8 | 5% |
| CVE-2025-6558 CISA KEV | Google · Chromium Google Chromium ANGLE and GPU Improper Input Validation VulnerabilityCISA remediation due for federal agencies: Aug 12, 2025 | Jul 21, 2025 | 6 days | High 8.8 | 11% |
| CVE-2025-6554 CISA KEV | Google · Chromium V8 Google Chromium V8 Type Confusion VulnerabilityCISA remediation due for federal agencies: Jul 23, 2025 | Jul 2, 2025 | 2 days | High 8.1 | 14% |
| CVE-2025-5419 CISA KEV | Google · Chromium V8 Google Chromium V8 Out-of-Bounds Read and Write VulnerabilityCISA remediation due for federal agencies: Jun 26, 2025 | Jun 5, 2025 | 3 days | High 8.8 | 8% |
| CVE-2025-2783 CISA KEV | Google · Chromium Mojo Google Chromium Mojo Sandbox Escape VulnerabilityCISA remediation due for federal agencies: Apr 17, 2025 | Mar 27, 2025 | 1 day | High 8.3 | 9% |
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.