# CVE-2023-4863 — Google Chrome

**CISA KEV**

> As of 2026-07-05, CVE-2023-4863 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 99.9% (99.9th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-09-13), with a US federal remediation deadline of 2023-10-04. Threadlinqs Intelligence links 3 tracked threat campaigns to CVE-2023-4863, most recently “Browser-Only Ransomware (InfernoGrabber v9.0) Abuses Chrome File System Access API to Encrypt Android Photos”.

**Last updated:** 2026-07-05

## What is CVE-2023-4863?

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)

The record classifies CVE-2023-4863 under weakness class [CWE-787](https://intel.threadlinqs.com/cwe/CWE-787). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 2 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 1164 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.8 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 99.9% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
- **CISA KEV:** Listed since 2023-09-13, federal remediation deadline 2023-10-04
- **Threadlinqs priority:** 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- **Published:** 2023-09-12

## Is CVE-2023-4863 being exploited?

CISA added CVE-2023-4863 to the Known Exploited Vulnerabilities catalog on 2023-09-13, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2023-10-04 under BOD 22-01. Weaponised exploit code for CVE-2023-4863 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 58 in the Threadlinqs vulnerability feed.

- [mistymntncop/CVE-2023-4863](https://github.com/mistymntncop/CVE-2023-4863) (github)
- [LiveOverflow/webp-CVE-2023-4863](https://github.com/LiveOverflow/webp-CVE-2023-4863) (github)
- [caoweiquan322/NotEnough](https://github.com/caoweiquan322/NotEnough) (github)
- [murphysecurity/libwebp-checker](https://github.com/murphysecurity/libwebp-checker) (github)
- [bbaranoff/CVE-2023-4863](https://github.com/bbaranoff/CVE-2023-4863) (github)
- [GTGalaxi/ElectronVulnerableVersion](https://github.com/GTGalaxi/ElectronVulnerableVersion) (github)
- [OITApps/Find-VulnerableElectronVersion](https://github.com/OITApps/Find-VulnerableElectronVersion) (github)
- [huiwen-yayaya/CVE-2023-4863](https://github.com/huiwen-yayaya/CVE-2023-4863) (github)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome, libwebp

Affected software packages:

- `rust:libwebp-sys2` — patched in 0.1.8
- `rust:libwebp-sys` — patched in 0.9.3
- `npm:electron` — patched in 22.3.24
- `npm:electron` — patched in 24.8.3
- `npm:electron` — patched in 25.8.1
- `npm:electron` — patched in 26.2.1
- `npm:electron` — patched in 27.0.0-beta.2
- `nuget:SkiaSharp` — patched in 2.88.6
- `pip:Pillow` — patched in 10.0.1
- `rust:webp` — patched in 0.2.6
- `nuget:magick.net-q16-anycpu` — patched in 13.3.0
- `nuget:magick.net-q16-hdri-anycpu` — patched in 13.3.0

## How to fix CVE-2023-4863

Fixed versions are recorded for 19 packages: rust:libwebp-sys2 0.1.8, rust:libwebp-sys 0.9.3, npm:electron 22.3.24, npm:electron 24.8.3, npm:electron 25.8.1, npm:electron 26.2.1, npm:electron 27.0.0-beta.2, nuget:SkiaSharp 2.88.6, pip:Pillow 10.0.1, rust:webp 0.2.6. Because CVE-2023-4863 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2023-10-04. No vendor patch reference has been recorded for CVE-2023-4863 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2023-4863

3 tracked threats in the Threadlinqs corpus reference CVE-2023-4863, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Browser-Only Ransomware (InfernoGrabber v9.0) Abuses Chrome File System Access API to Encrypt Android Photos](https://intel.threadlinqs.com/threat/TL-2026-1119) — MEDIUM · 2026-07-05
- [AI-Generated Browser-Only Ransomware Abuses Chrome File System Access API (InfernoGrabber 9000 / DeepSeek)](https://intel.threadlinqs.com/threat/TL-2026-1129) — MEDIUM · 2026-07-05
- [InfernoGrabber v9.0: AI-Generated In-Browser Ransomware Abusing the Chromium File System Access API](https://intel.threadlinqs.com/threat/TL-2026-1051) — MEDIUM · 2026-07-01

## Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html)
- [crbug.com](https://crbug.com/1479274)
- [en.bandisoft.com](https://en.bandisoft.com/honeyview/history/)
- [stackdiary.com](https://stackdiary.com/critical-vulnerability-in-webp-codec-cve-2023-4863/)
- [mozilla.org](https://www.mozilla.org/en-US/security/advisories/mfsa2023-40/)

_Showing 5 of 20 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2023-4863
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
