Exploited CVEs / Google / CVE-2026-58704
CVE-2026-58704
Google Pixel Improper Authorization Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-09-19; treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Chrome Releases (security updates), linked below.
Risk summary
Actively exploited Google Pixel vulnerability, High severity, CVSS v3 8.8. Added to the CISA KEV catalog 2026-09-16.
Senserva AI Opinion and rich prompt for CVE-2026-58704
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-58704
- Published
- 2026-09-16
- Last revised
- 2026-09-16
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2026-09-19.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Official fix for CVE-2026-58704
The authoritative fix and affected-version list are published by the vendor. Find the Pixel advisory on Chrome Releases (security updates).
Common questions about CVE-2026-58704
Is CVE-2026-58704 actively exploited?
Yes. CVE-2026-58704 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-09-16, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.
What is the CISA deadline and required action for CVE-2026-58704?
CISA set the federal (BOD 22-01) remediation due date at 2026-09-19. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
What fixes CVE-2026-58704?
The authoritative fix is in the vendor advisory: see Chrome Releases (security updates) for the patched Pixel versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-58704?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-58704's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (morning and afternoon US Central).
Scope and sources
- More exploited Google CVEs
- CVE-2026-87491CVE-2026-85046CVE-2026-11645CVE-2026-5281CVE-2026-3910CVE-2026-3909CVE-2026-2441CVE-2025-14174
All Google exploited CVEs on one page: Google vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.