Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-4450: Out of bounds write in Google Chrome

0
Unknown
VulnerabilityCVE-2026-4450cvecve-2026-4450
Published: Fri Mar 20 2026 (03/20/2026, 01:34:50 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Out of bounds write in V8 in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 03/20/2026, 02:43:16 UTC

Technical Analysis

CVE-2026-4450 is an out-of-bounds write vulnerability discovered in the V8 JavaScript engine component of Google Chrome, affecting all versions prior to 146.0.7680.153. The vulnerability arises from improper bounds checking during memory operations within V8, which can be triggered by processing a specially crafted HTML page containing malicious JavaScript code. This flaw enables an attacker to corrupt the heap memory, potentially leading to arbitrary code execution within the context of the browser process. Since V8 is responsible for executing JavaScript, exploitation can allow attackers to bypass security mechanisms, escalate privileges within the browser sandbox, or execute malicious payloads remotely. The vulnerability does not require user authentication but does require user interaction in the form of visiting a malicious website. Although no active exploits have been reported, the high severity rating by Chromium security indicates the potential for serious impact. The vulnerability affects a broad user base given Chrome's dominant market share in desktop and mobile browsers worldwide. The lack of a CVSS score necessitates an assessment based on the technical details, which indicate a high risk due to the potential for remote code execution and widespread exposure. The issue was publicly disclosed on March 20, 2026, with a patch available in Chrome version 146.0.7680.153. Organizations should apply this update promptly to prevent exploitation.

Potential Impact

The primary impact of CVE-2026-4450 is the potential for remote code execution through heap corruption, which can compromise the confidentiality, integrity, and availability of affected systems. Successful exploitation could allow attackers to execute arbitrary code within the browser context, potentially leading to data theft, session hijacking, installation of malware, or lateral movement within a network. Given Chrome's extensive use in enterprise and consumer environments, the vulnerability poses a significant risk to organizations worldwide, especially those handling sensitive data or critical infrastructure. The attack vector is remote and requires only that a user visits a malicious web page, increasing the likelihood of exploitation. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits following public disclosure. The vulnerability could also be leveraged in targeted attacks against high-value targets or in widespread phishing campaigns. Overall, the impact is high due to the ease of exploitation and the broad scope of affected users.

Mitigation Recommendations

To mitigate CVE-2026-4450, organizations and users should immediately update Google Chrome to version 146.0.7680.153 or later, where the vulnerability has been patched. Beyond patching, organizations should implement web filtering solutions to block access to known malicious websites and employ endpoint detection and response (EDR) tools to monitor for suspicious browser behaviors indicative of exploitation attempts. Network-level protections such as DNS filtering and intrusion prevention systems (IPS) can help reduce exposure to malicious web content. Security teams should educate users about the risks of visiting untrusted websites and encourage safe browsing practices. Additionally, enabling browser sandboxing and restricting unnecessary browser extensions can reduce the attack surface. Regular vulnerability scanning and penetration testing should include checks for outdated browser versions. Finally, organizations should maintain an incident response plan to quickly address any suspected compromise resulting from browser-based attacks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-03-19T20:23:50.820Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69bcafd7e32a4fbe5f174c93

Added to database: 3/20/2026, 2:24:23 AM

Last enriched: 3/20/2026, 2:43:16 AM

Last updated: 3/20/2026, 5:44:55 AM

Views: 14

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses