CVE-2023-4863

KEVGoogle Chromium WebP Heap-Based Buffer Overflow Vulnerability

Description

Google Chromium WebP contains a heap-based buffer overflow vulnerability that allows a remote attacker to perform an out-of-bounds memory write via a crafted HTML page. This vulnerability can affect applications that use the WebP Codec.

Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

PublishedSep 12, 2023

Last modifiedJun 17, 2026

Added to KEVSep 13, 2023

Remediation dueOct 4, 2023

References

openwall.com/lists/oss-security/2023/09/21/4Mailing List
openwall.com/lists/oss-security/2023/09/22/1Mailing List
openwall.com/lists/oss-security/2023/09/22/3Mailing List
openwall.com/lists/oss-security/2023/09/22/4Mailing List
openwall.com/lists/oss-security/2023/09/22/5Mailing List
openwall.com/lists/oss-security/2023/09/22/6Mailing List
openwall.com/lists/oss-security/2023/09/22/7Mailing List
openwall.com/lists/oss-security/2023/09/22/8Mailing List
openwall.com/lists/oss-security/2023/09/26/1Mailing List
openwall.com/lists/oss-security/2023/09/26/7Mailing List
openwall.com/lists/oss-security/2023/09/28/1Mailing List
openwall.com/lists/oss-security/2023/09/28/2Mailing List

0 recent articles mention this CVE

Risk assessment · Critical

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 1118 days
CVSS: 8.8 HIGH
EPSS (30-day exploit probability): 100.0% · top 1% of all CVEs
Weakness: CWE-787
Attack vector: Network, remotely reachable

Recommended actions

1.Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.