How severe is CVE-2023-5217?

CVE-2023-5217 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-5217?

CVE-2023-5217 affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix CVE-2023-5217?

Update electron to version 22.3.25 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2023-5217 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2023-5217, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-5217?

CVE-2023-5217 has an EPSS (Exploit Prediction Scoring System) score of 5.0%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2023-5217 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-5217 (Google Chromium libvpx Heap Buffer Overflow Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-10-02. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-10-23. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2023-5217?

CVE-2023-5217 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-5217 published, and has it been updated?

CVE-2023-5217 was published on September 28, 2023 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-10-02 — agencies required to remediate by 2023-10-23

📦 npm

CVE-2023-5217

HIGH

Electron affected by libvpx's heap buffer overflow in vp8 encoding

Also known asGHSA-qqvq-6xgj-jw8g

Published

Sep 28, 2023

Updated

Apr 16, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

9 known

EPSS Exploitation Probability

via FIRST.org ↗

5.0%probability of exploitation in next 30 days

Lower Risk90th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

📦electron📦electron📦electron📦electron📦electron

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	22.3.25
📦npm	`electron`	≥ 24.0.0&&< 24.8.5	24.8.5
📦npm	`electron`	≥ 25.0.0&&< 25.8.4	25.8.4
📦npm	`electron`	≥ 26.0.0&&< 26.2.4	26.2.4
📦npm	`electron`	≥ 27.0.0-alpha.1&&< 27.0.0-beta.8	27.0.0-beta.8

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.