Electron affected by libvpx's heap buffer overflow in vp8 encodingGHSA-qqvq-6xgj-jw8g
HIGHFix: electron/electron#40022GHSA-qqvq-6xgj-jw8g is a high-severity (CVSS 8.8) Out-of-bounds Write vulnerability in electron. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-10-02) — treat it as actively exploited and patch now. A fix is available for electron — see the affected versions and patch details below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-10-02. Federal agencies were required to remediate by 2023-10-23.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-qqvq-6xgj-jw8g.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-qqvq-6xgj-jw8g by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
electronnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | electron | all versions | 22.3.25npm install electron@22.3.25 |
| 📦npm | electron | ≥ 24.0.0&&< 24.8.5 | 24.8.5npm install electron@24.8.5 |
| 📦npm | electron | ≥ 25.0.0&&< 25.8.4 | 25.8.4npm install electron@25.8.4 |
| 📦npm | electron | ≥ 26.0.0&&< 26.2.4 | 26.2.4npm install electron@26.2.4 |
| 📦npm | electron | ≥ 27.0.0-alpha.1&&< 27.0.0-beta.8 | 27.0.0-beta.8npm install electron@27.0.0-beta.8 |
Affected Products
ipadosappleiphone osappledebian linuxdebianfedorafedoraprojectchromegoogleedgemicrosoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 22.3.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqvq-6xgj-jw8g is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This security issue has been classified as having an Important security impact. Desktop users are at a high risk of exploitation of this flaw with very minimal interaction. It may compromise the confidentiality, integrity, or availability of resources. Customers using this application, which does server-side video…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-qqvq-6xgj-jw8g (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 7 | thunderbird-0:115.3.1-1.el7_9 | RHSA-2023:5475 |
| Red Hat Enterprise Linux 7 | firefox-0:115.3.1-1.el7_9 | RHSA-2023:5477 |
| Red Hat Enterprise Linux 8 | thunderbird-0:115.3.1-1.el8_8 | RHSA-2023:5428 |
| Red Hat Enterprise Linux 8 | firefox-0:115.3.1-1.el8_8 | RHSA-2023:5433 |
| Red Hat Enterprise Linux 8 | libvpx-0:1.7.0-10.el8_8 | RHSA-2023:5537 |
| Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions | thunderbird-0:115.3.1-1.el8_1 | RHSA-2023:5438 |
| Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions | firefox-0:115.3.1-1.el8_1 | RHSA-2023:5440 |
| Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions | libvpx-0:1.7.0-8.el8_1 | RHSA-2023:5535 |
Frequently Asked Questions
Is GHSA-qqvq-6xgj-jw8g in your dependencies?
Find it across npm, including transitive dependencies.