CVE-2023-5217: Heap Buffer Overflow in libvpx VP8 Encoding
- Vendors
- GoogleDebian ProjectFaradayMicrosoft CorporationFedora ProjectMozillaAppleWebmproject
CVE-2023-5217 is a heap-based buffer overflow in the VP8 encoding functionality of libvpx, affecting Google Chrome before 117.0.5938.132 and other applications incorporating vulnerable library versions. A remote attacker can use a crafted HTML page to exercise the vulnerable encoding path and potentially exploit heap corruption, resulting in application crashes or arbitrary code execution. The upstream fix is included in libvpx 1.13.1. The vulnerability has been exploited in the wild and is associated with Candiru's DevilsTongue spyware.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can cause denial of service or arbitrary code execution in the affected application process, potentially compromising the confidentiality and integrity of information accessible to that process. The ultimate impact depends on application privileges and isolation boundaries; this vulnerability alone does not establish a sandbox escape or operating-system privilege escalation.
Mitigation
If you can’t patch tonight, do this now.
Until updates can be deployed, restrict affected browsers and embedded Chromium applications from rendering untrusted web content, including through navigation allowlists. For older Chromium-based applications, disabling WebCodecs with --disable-blink-features=WebCodecs is a documented workaround for that exposure path; it should not be treated as a complete fix for every application or encoding interface. Maintain sandboxing and least-privilege controls to limit exploitation impact. These measures do not replace updating the vulnerable library and bundled copies.
Remediation
Patch, then assume compromise.
Upgrade libvpx to 1.13.1 or later, or install the operating-system vendor's package containing the backported fix. Update applications that bundle libvpx rather than relying solely on a system-library update. Fixed application versions include Google Chrome 117.0.5938.132, Microsoft Edge 117.0.2045.47, Edge Extended Stable 116.0.1938.98, CefSharp.Common and CefSharp.Common.NETCore 117.2.20, iOS/iPadOS 17.0.3, and iOS/iPadOS 16.7.1 for the corresponding supported branch. Electron fixes are available in 22.3.25, 24.8.5, 25.8.4, 26.2.4, and 27.0.0-beta.8. Prefer current supported releases containing these fixes. For CIQ LTS deployments, apply the libvpx package updates specified by the applicable CIQ advisory.
Exploits
1 exploit validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2023-5217 exploited in the wild?
- Yes. As of Oct 29, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 2, 2023.
- Is there a public exploit for CVE-2023-5217?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2023-5217, the earliest disclosed Oct 6, 2023.
- Is there a patch for CVE-2023-5217?
- Upgrade libvpx to 1.13.1 or later, or install the operating-system vendor's package containing the backported fix. Update applications that bundle libvpx rather than relying solely on a system-library update.
- What products are affected by CVE-2023-5217?
- Google Chrome, Webmproject Libvpx, Debian Project Debian Linux, Faraday Edge, Microsoft Corporation Edge, and 7 more.
- How severe is CVE-2023-5217?
- CVE-2023-5217 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 49.0% (99th percentile) as of Oct 29, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.