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-4444: Stack buffer overflow in Google Chrome

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

Description

Stack buffer overflow in WebRTC in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit stack corruption via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 19:24:41 UTC

Technical Analysis

CVE-2026-4444 is a stack buffer overflow vulnerability identified in the WebRTC component of Google Chrome before version 146.0.7680.153. WebRTC (Web Real-Time Communication) is a widely used technology enabling real-time audio, video, and data communication directly between browsers without plugins. The vulnerability arises from improper handling of data within the WebRTC stack, allowing an attacker to craft a malicious HTML page that triggers stack corruption. This corruption can lead to arbitrary code execution in the context of the browser process, potentially allowing attackers to execute malicious payloads, steal sensitive information, or disrupt browser functionality. The flaw requires no prior authentication but does require user interaction, such as visiting a malicious or compromised website. The CVSS v3.1 base score of 8.8 reflects the vulnerability's high impact on confidentiality, integrity, and availability, combined with its ease of exploitation over the network with low complexity and no privileges required. Although no exploits have been reported in the wild yet, the vulnerability's presence in a core browser component used globally makes it a significant threat. The vulnerability was publicly disclosed on March 20, 2026, and Google has released a patched version (146.0.7680.153) to address the issue. Organizations relying on Chrome for secure communications, especially those using WebRTC for conferencing or real-time data transfer, are particularly vulnerable.

Potential Impact

The impact of CVE-2026-4444 is substantial due to the widespread use of Google Chrome and the critical role of WebRTC in enabling real-time communications. Successful exploitation can lead to arbitrary code execution within the browser, allowing attackers to bypass security controls, access sensitive data, or disrupt services. This can compromise user privacy, lead to data breaches, and facilitate further network intrusion. Enterprises using Chrome for internal communications or customer interactions may face operational disruptions and reputational damage. The vulnerability affects all users running vulnerable Chrome versions, making it a broad threat. Given the network attack vector and lack of required privileges, attackers can target users globally with minimal barriers. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the urgency for patching, as exploit development could emerge rapidly.

Mitigation Recommendations

To mitigate CVE-2026-4444, organizations and users should immediately update Google Chrome to version 146.0.7680.153 or later, where the vulnerability is patched. Enterprises should enforce browser update policies and consider deploying endpoint management tools to ensure compliance. Network defenses can be enhanced by monitoring and filtering suspicious WebRTC traffic and employing web content filtering to block access to untrusted or malicious websites. Security teams should audit WebRTC usage within their environments and educate users about the risks of interacting with unknown web content. Additionally, employing browser sandboxing and endpoint detection and response (EDR) solutions can help detect and contain exploitation attempts. Regular vulnerability scanning and penetration testing should include checks for outdated browser versions. Organizations should also stay informed about any emerging exploit reports related to this vulnerability.

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:49.144Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69bcafd6e32a4fbe5f174c42

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

Last enriched: 3/27/2026, 7:24:41 PM

Last updated: 5/4/2026, 5:34:44 AM

Views: 94

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 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