CVE-2026-79223
8.8Google · Chrome
An integer overflow vulnerability in the Chromium engine within Google Chrome allows remote attackers to read sensitive memory via a crafted file.
Executive summary
Google Chrome versions prior to 152.0.7977.65 are susceptible to an integer overflow vulnerability that could allow unauthorized memory access.
Vulnerability
This vulnerability is an integer overflow flaw (CWE-190) occurring within the Chromium engine. It allows an unauthenticated, remote attacker to read memory within the browser sandbox by enticing a user to open a specially crafted file.
Business impact
The ability for an attacker to read memory within the sandbox poses a significant risk to data confidentiality. Although the CVSS score is 8.8, indicating a high severity, the requirement for user interaction limits the immediate exploitability. Successful exploitation could lead to the exposure of sensitive session tokens, credentials, or other private information stored in the browser memory, potentially facilitating further attacks against the user.
Remediation
Immediate Action: Update all instances of Google Chrome to version 152.0.7977.65 or later to incorporate the vendor-supplied security fixes.
Proactive Monitoring: Monitor network traffic for unusual file downloads or access patterns associated with the browser, and review local endpoint logs for unexpected application crashes that may indicate exploitation attempts.
Compensating Controls: Ensure that the browser sandbox environment is properly configured and that users are trained to exercise caution when opening files from untrusted sources, which serves as a primary defense against this vector.
Exploitation status
Public Exploit Available: No (exploit_available: false)
Analyst recommendation
Given the high CVSS score and the potential for unauthorized memory access, this vulnerability should be treated with high priority. IT administrators must ensure that all Google Chrome installations are updated to the patched version as soon as possible to mitigate the risk of memory disclosure. Relying on browser-based security alone is insufficient, and prompt patching remains the most effective strategy for protection.