Summary
Heap buffer overflow in libwebp allow a remote attacker to perform an out of bounds memory write 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-4863 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 (0.1.8, 0.9.3, 22.3.24, 24.8.3, 25.8.1, 26.2.1, 27.0.0-beta.2, 2.88.6, 10.0.1, 0.2.6, 13.3.0, 0.0.0-20250406010349-76805d5a8860, 1.4.0, 1.1.2-0.20250406010349-76805d5a8860); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Remediation advice
libwebp-sys2 to 0.1.8 or later; libwebp-sys to 0.9.3 or later; electron to 22.3.24 or later; electron to 24.8.3 or later; electron to 25.8.1 or later; electron to 26.2.1 or later; electron to 27.0.0-beta.2 or later; SkiaSharp to 2.88.6 or later; Pillow to 10.0.1 or later; webp to 0.2.6 or later; magick.net-q16-anycpu to 13.3.0 or later; magick.net-q16-hdri-anycpu to 13.3.0 or later; magick.net-q16-x64 to 13.3.0 or later; magick.net-q8-anycpu to 13.3.0 or later; magick.net-q8-openmp-x64 to 13.3.0 or later; magick.net-q8-x64 to 13.3.0 or later; github.com/chai2010/webp to 0.0.0-20250406010349-76805d5a8860 or later; github.com/chai2010/webp to 1.4.0 or later; github.com/chai2010/webp to 1.1.2-0.20250406010349-76805d5a8860 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2023-4863? CVE-2023-4863 is a high-severity out-of-bounds write vulnerability in libwebp-sys2 (rust), affecting versions < 0.1.8. It is fixed in 0.1.8, 0.9.3, 22.3.24, 24.8.3, 25.8.1, 26.2.1, 27.0.0-beta.2, 2.88.6, 10.0.1, 0.2.6, 13.3.0, 0.0.0-20250406010349-76805d5a8860, 1.4.0, 1.1.2-0.20250406010349-76805d5a8860. A write operation targets a memory location beyond the intended buffer boundary.
- How severe is CVE-2023-4863? CVE-2023-4863 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 packages are affected by CVE-2023-4863?
libwebp-sys2(rust) (versions < 0.1.8)libwebp-sys(rust) (versions < 0.9.3)electron(npm) (versions >= 22.0.0, < 22.3.24)SkiaSharp(nuget) (versions >= 2.0.0, < 2.88.6)Pillow(pip) (versions < 10.0.1)webp(rust) (versions < 0.2.6)magick.net-q16-anycpu(nuget) (versions < 13.3.0)magick.net-q16-hdri-anycpu(nuget) (versions < 13.3.0)magick.net-q16-x64(nuget) (versions < 13.3.0)magick.net-q8-anycpu(nuget) (versions < 13.3.0)magick.net-q8-openmp-x64(nuget) (versions < 13.3.0)magick.net-q8-x64(nuget) (versions < 13.3.0)github.com/chai2010/webp(go) (versions < 0.0.0-20250406010349-76805d5a8860)
- Is there a fix for CVE-2023-4863? Yes. CVE-2023-4863 is fixed in 0.1.8, 0.9.3, 22.3.24, 24.8.3, 25.8.1, 26.2.1, 27.0.0-beta.2, 2.88.6, 10.0.1, 0.2.6, 13.3.0, 0.0.0-20250406010349-76805d5a8860, 1.4.0, 1.1.2-0.20250406010349-76805d5a8860. Upgrade to this version or later.
- Is CVE-2023-4863 exploitable, and should I be worried? Whether CVE-2023-4863 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-4863 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-4863?
- Upgrade
libwebp-sys2to 0.1.8 or later - Upgrade
libwebp-systo 0.9.3 or later - Upgrade
electronto 22.3.24 or later - Upgrade
electronto 24.8.3 or later - Upgrade
electronto 25.8.1 or later - Upgrade
electronto 26.2.1 or later - Upgrade
electronto 27.0.0-beta.2 or later - Upgrade
SkiaSharpto 2.88.6 or later - Upgrade
Pillowto 10.0.1 or later - Upgrade
webpto 0.2.6 or later - Upgrade
magick.net-q16-anycputo 13.3.0 or later - Upgrade
magick.net-q16-hdri-anycputo 13.3.0 or later - Upgrade
magick.net-q16-x64to 13.3.0 or later - Upgrade
magick.net-q8-anycputo 13.3.0 or later - Upgrade
magick.net-q8-openmp-x64to 13.3.0 or later - Upgrade
magick.net-q8-x64to 13.3.0 or later - Upgrade
github.com/chai2010/webpto 0.0.0-20250406010349-76805d5a8860 or later - Upgrade
github.com/chai2010/webpto 1.4.0 or later - Upgrade
github.com/chai2010/webpto 1.1.2-0.20250406010349-76805d5a8860 or later
- Upgrade