Skip to content
skopnix

CVE-2023-5217 · Published 28 Sep 2023

Google Chromium libvpx

On CISA's KEV list 4 days after disclosure; 4 public exploits.

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.

CISA required action (federal due date 23 Oct 2023): Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Signals

KEV, exploited in the wild
yes, added 2 Oct 2023, due 23 Oct 2023
EPSS, 30-day forecast
49%, 99th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 28 Sep 2023 to today

4 days from disclosure to the KEV listing
20252026Disclosed 28 Sep 2023KEV 2 Oct 2023First PoC 6 Oct 2023today
  1. Disclosed
  2. KEV+4 d
  3. First PoC+4 d

4 days from disclosure to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 4 known · links only

GitHub PoCs 4Metasploit 0Exploit-DB 0

GitHub PoCs, by trust then stars4

  1. A PoC to trigger CVE-2023-5217 from the Browser WebCodecs or MediaRecorder interface.

    created 6 Oct 2023

  2. created 6 Oct 2023

  3. created 6 Oct 2023

  4. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check