What is CVE-2023-5217?

CVE-2023-5217 is a high-severity out-of-bounds write vulnerability in electron (npm), affecting versions < 22.3.25. It is fixed in 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8. A write operation targets a memory location beyond the intended buffer boundary.

How severe is CVE-2023-5217?

CVE-2023-5217 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of electron are affected by CVE-2023-5217?

electron (npm) versions < 22.3.25 is affected.

Is there a fix for CVE-2023-5217?

Yes. CVE-2023-5217 is fixed in 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8. Upgrade to this version or later.

Is CVE-2023-5217 exploitable, and should I be worried?

Whether CVE-2023-5217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-5217 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-5217 in electron | Intelligent Application Security

Q: How severe is CVE-2023-5217?

CVE-2023-5217 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of electron are affected by CVE-2023-5217?

electron (npm) versions < 22.3.25 is affected.

Q: Is there a fix for CVE-2023-5217?

Yes. CVE-2023-5217 is fixed in 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8. Upgrade to this version or later.

Q: Is CVE-2023-5217 exploitable, and should I be worried?

Whether CVE-2023-5217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-5217 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-5217?

Upgrade: electron to 22.3.25 or later, electron to 24.8.5 or later, electron to 25.8.4 or later, electron to 26.2.4 or later, electron to 27.0.0-beta.8 or later.

Summary

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.

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2023-5217 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8); upgrading removes the vulnerable code path.

Affected versions

electron (< 22.3.25) electron (>= 24.0.0, < 24.8.5) electron (>= 25.0.0, < 25.8.4) electron (>= 26.0.0, < 26.2.4) electron (>= 27.0.0-alpha.1, < 27.0.0-beta.8)

Security releases

electron → 22.3.25 (npm) electron → 24.8.5 (npm) electron → 25.8.4 (npm) electron → 26.2.4 (npm) electron → 27.0.0-beta.8 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

electron to 22.3.25 or later; electron to 24.8.5 or later; electron to 25.8.4 or later; electron to 26.2.4 or later; electron to 27.0.0-beta.8 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-5217? CVE-2023-5217 is a high-severity out-of-bounds write vulnerability in electron (npm), affecting versions < 22.3.25. It is fixed in 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8. A write operation targets a memory location beyond the intended buffer boundary.
How severe is CVE-2023-5217? CVE-2023-5217 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of electron are affected by CVE-2023-5217? electron (npm) versions < 22.3.25 is affected.
Is there a fix for CVE-2023-5217? Yes. CVE-2023-5217 is fixed in 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8. Upgrade to this version or later.
Is CVE-2023-5217 exploitable, and should I be worried? Whether CVE-2023-5217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-5217 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-5217?
- Upgrade electron to 22.3.25 or later
- Upgrade electron to 24.8.5 or later
- Upgrade electron to 25.8.4 or later
- Upgrade electron to 26.2.4 or later
- Upgrade electron to 27.0.0-beta.8 or later

Other vulnerabilities in electron

CVE-IDSeverityPackage summary

CVE-2026-54257Criticalelectron: Electron: Buffer performs incorrect byte length calculations resulting in heap buffer under/overflow CVE-2026-34781Lowelectron: Electron: Crash in clipboard.readImage() on malformed clipboard image data CVE-2026-34765Mediumelectron: Electron: Named window.open targets not scoped to the opener's browsing context CVE-2026-34764Lowelectron: Electron: Use-after-free in offscreen shared texture release() callback CVE-2026-34780Highelectron: Electron: Context Isolation bypass via contextBridge VideoFrame transfer