Google Chrome CVE-2026-79223

Exploitation requires the victim to open a specially crafted file in Google Chrome - CVSS UI:R confirms this active user-interaction prerequisite, meaning drive-by exploitation without file-open interaction is not indicated. No authentication or elevated privileges are required (PR:N), so any Chrome user who opens the malicious file on an affected version is exposed. No non-default configuration is required; any desktop Chrome installation prior to 152.0.7977.65 processing the targeted file type is potentially vulnerable. Critical limiting factors: the attack is bounded to memory within the Chromium renderer sandbox (S:U - no scope change), providing only in-sandbox information disclosure without OS-level access or sandbox escape on its own; a second independent vulnerability would be required to chain to full system compromise. SSVC Automatable:no indicates the file-delivery-and-open sequence is not easily scripted for mass exploitation.

Multiple intelligence signals conflict in this case, and the discrepancy itself is the most important risk signal. The NVD CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is internally inconsistent with the CVE description: an in-sandbox memory read does not plausibly produce I:H (integrity) or A:H (availability) impact, and S:U confirms no sandbox escape - suggesting NVD scoring is over-stated. Google's Chromium team, with access to full vulnerability details, independently rates this Low severity, which is a stronger and more credible signal. EPSS at 0.16% (5th percentile) and SSVC Exploitation:none corroborate a very low real-world exploitation probability. SSVC Technical Impact is rated 'total,' which likely reflects potential chaining scenarios rather than standalone exploitability; SSVC Automatable:no further limits mass-exploitation feasibility. There is no CISA KEV listing and no public exploit identified at time of analysis. Net assessment: this is a patch-priority vulnerability important to remediate on a normal patch cycle, not an emergency requiring immediate incident response. The realistic priority is driven by Chrome's ubiquitous deployment rather than inherent exploit sophistication.

An attacker crafts a malicious file containing integer values designed to overflow a size or length field in a Chromium file-format parser. The file is delivered to the target - via a malicious web page, email attachment, or shared document - and the victim opens it in Chrome, triggering the integer overflow in the sandboxed renderer process and enabling an out-of-bounds memory read. The attacker may leverage leaked in-sandbox memory contents as an ASLR or heap-layout disclosure primitive to stage a subsequent, higher-severity exploit such as a remote code execution or sandbox escape; used in isolation, the flaw yields only in-sandbox information disclosure. No public exploit code has been identified at time of analysis.