HighGHSA-qqvq-6xgj-jw8gCVE-2023-5217

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

Published 28 Sept 2023 · Updated 10 Sept 2026

Affected packages

Affected
<22.3.25
Fixed in
22.3.25
Update to the fixed version for your release line, for example:npm install electron@22.3.25
Affected
>=24.0.0 <24.8.5
Fixed in
24.8.5
Update to the fixed version for your release line, for example:npm install electron@24.8.5
Affected
>=25.0.0 <25.8.4
Fixed in
25.8.4
Update to the fixed version for your release line, for example:npm install electron@25.8.4
Affected
>=26.0.0 <26.2.4
Fixed in
26.2.4
Update to the fixed version for your release line, for example:npm install electron@26.2.4
Affected
>=27.0.0-alpha.1 <27.0.0-beta.8
Fixed in
27.0.0-beta.8
Update to the fixed version for your release line, for example:npm install electron@27.0.0-beta.8

Details

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.

Is GHSA-qqvq-6xgj-jw8g in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.