Exploited CVEs / Google / CVE-2023-5217

CVE-2023-5217

Actively exploited Google Chromium libvpx vulnerability, High severity, CVSS 8.8. Added to the CISA KEV catalog 2023-10-02.

Google Chromium libvpx Heap Buffer Overflow Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2023-10-23 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Chrome Releases (security updates), linked below.

HighCISA KEV

Risk summary

CVSS base
8.8
EPSS exploit probability
49%
Severity
High
Added to KEV
2023-10-02
CISA due date
2023-10-23 (past due)

Ask your own AI about CVE-2023-5217

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

CISA required action

Federal (BOD 22-01) remediation due date: 2023-10-23 (past due).

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Official fix for CVE-2023-5217

The authoritative fix and affected-version list are published by the vendor. Find the Chromium libvpx advisory on Chrome Releases (security updates).

Chrome Releases (security updates)CISA KEV entry

Common questions about CVE-2023-5217

Is CVE-2023-5217 actively exploited?

Yes. CVE-2023-5217 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2023-10-02, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 49%.

What is the CISA deadline and required action for CVE-2023-5217?

CISA set the federal (BOD 22-01) remediation due date at 2023-10-23, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2023-5217?

The authoritative fix is in the vendor advisory: see Chrome Releases (security updates) for the patched Chromium libvpx 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-2023-5217?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2023-5217'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 daily.

More exploited Google CVEs

The newest Google entries on the CISA KEV catalog:

CVE-2026-11645CVE-2026-5281CVE-2026-3910CVE-2026-3909CVE-2026-2441CVE-2025-14174CVE-2025-13223CVE-2025-10585

All Google exploited CVEs on one page: Google vulnerabilities actively exploited.

Authoritative references

CVE recordNVD detailCISA KEV catalogFIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

Sponsored by Senserva

Siemserva by Senserva reports patch status for your own devices: which ones are exposed to CVE-2023-5217, for example, ranked by what attackers actually exploit.

  • Patch status in one scan: which devices are affected, which are not
  • Missing updates ranked by CISA KEV and EPSS, so you fix the right things first
  • Data from Intune, Microsoft Defender, Windows Autopatch, and Azure Update Manager, with more sources on the way
  • Third-party app patching too: updates published to Intune by PatchMyPC, Scappman, Robopack, or any vendor, read vendor-neutrally
  • Optional AI Enhanced Reporting: plain-language summaries and recommended next steps written into your reports
  • Then go further: 650+ security checks, compliance evidence, and Senserva Trustworthy AI driven configuration remediation
Patch Status Report
CVE-2023-5217 exposure across 110 devices, ranked by exploitation
23
EXPOSED TO CVE-2023-5217
87
UP TO DATE
41
OTHER UPDATES DUE
UPDATESEVERITYKEVMISSING
CVE-2023-5217CriticalEXPLOITED23
KB5094142High-11
KB5094139High-6
Estimated report, sample data for illustration
Get Going with Senserva Senserva patching Built for IT admins and security teams, with audit-ready data for compliance. Senserva is a Microsoft Intelligent Security Association member.
Senserva patching for Microsoft 365
Two minutes, click to play

Patching in action in two minutes. Watch page · All videos.

Lexicon: the terms on this page
CVE
Common Vulnerabilities and Exposures. A unique ID for one publicly known vulnerability, such as CVE-2025-1234.
KB
Microsoft Knowledge Base article. The identifier for a specific Microsoft update.
KEV
CISA Known Exploited Vulnerabilities. CVEs confirmed exploited in the wild. Fix these first.
CVSS
Common Vulnerability Scoring System. A standardized Severity score from 0 to 10.
EPSS
Exploit Prediction Scoring System. The probability a CVE will be exploited in the next 30 days.
MSRC
Microsoft Security Response Center. Microsoft's Patch Tuesday advisories and KB-to-CVE mapping.
NVD
National Vulnerability Database (NIST). Authoritative CVE metadata and CVSS scores.
Ransomware
The vulnerability is linked to known ransomware activity.
Reference: the Microsoft patching guide, how Intune, Windows Autopatch, Defender, and Azure Update Manager fit together.
Data notice: this page, the feeds, and the API are provided as is, for informational purposes only, without warranty of any kind. Senserva, LLC does not guarantee the accuracy, completeness, or timeliness of third-party data (MSRC, NVD, CISA KEV, EPSS) and accepts no liability for actions taken based on it; verify against the authoritative vendor advisory before acting. Built daily with Senserva Trustworthy AI. All use of this data is subject to the Senserva EULA.