CVE-2023-5217
Actively exploited. CVE-2023-5217 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-10-02) — exploitation has been observed in the wild, and US federal agencies are required to remediate it under BOD 22-01. Treat patching as urgent.
Public exploit code is available. Proof-of-concept or working exploit code for CVE-2023-5217 is indexed in GitHub PoC. Expect opportunistic scanning and exploitation attempts — prioritize remediation.
Google Chromium libvpx contains a heap buffer overflow vulnerability in vp8 encoding that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could impact web browsers using libvpx, including but not limited to Google Chrome.
CSIRTS triage
- What
- A heap buffer overflow vulnerability in libvpx allows remote exploitation via crafted HTML.
- Who is affected
- Users of web browsers using Google Chromium, including Google Chrome.
- Urgency
- Remediation is critical due to active exploitation and the severity of the vulnerability.
- Action
- Update to the latest version of Google Chrome or affected browsers.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2023-5217
Get an email if CVE-2023-5217 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Exploitation confirmedAlready exploited in the wild (CISA KEV) — the prediction phase is over. Patch now. Riskier than 99% of all EPSS-scored CVEs.
Exploit availability
Public exploit or proof-of-concept code for CVE-2023-5217 is indexed in these free datasets. Available exploit code raises real-world risk independent of the CVSS score.
- GitHub PoCPublic proof-of-concept repositories on GitHub reference this CVE.look it up ↗
Advisory coverage (1)
- criticalexploitedCVE-2023-5217: Google Chromium libvpx Heap Buffer Overflow Vulnerabilitycisa-kev · 2023-10-02
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2023-5217)