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-3922: Use after free in Google Chrome

0
High
VulnerabilityCVE-2026-3922cvecve-2026-3922
Published: Wed Mar 11 2026 (03/11/2026, 22:04:06 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Use after free in MediaStream in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 03/12/2026, 13:59:38 UTC

Technical Analysis

CVE-2026-3922 is a use-after-free vulnerability identified in the MediaStream component of Google Chrome, affecting versions prior to 146.0.7680.71. The flaw arises when the browser improperly manages memory related to MediaStream objects, leading to a use-after-free condition. An attacker can exploit this by delivering a crafted HTML page that triggers heap corruption, potentially allowing arbitrary code execution within the context of the browser process. This vulnerability is remotely exploitable without requiring authentication, but it does require user interaction, such as visiting a malicious or compromised website. The vulnerability impacts the confidentiality, integrity, and availability of the affected system by enabling attackers to execute arbitrary code, steal sensitive information, or cause denial of service. The CVSS v3.1 base score is 8.8, reflecting high severity due to the ease of exploitation (network vector, low attack complexity), no privileges required, and high impact on all security objectives. Although no known exploits have been reported in the wild yet, the nature of use-after-free vulnerabilities in browsers makes this a critical concern for users and organizations. The vulnerability was publicly disclosed on March 11, 2026, and Google has released a patched version 146.0.7680.71 to address the issue. The lack of patch links in the provided data suggests users should refer to official Google Chrome security advisories for updates. Given Chrome's widespread use globally, this vulnerability poses a significant risk to a broad user base.

Potential Impact

The potential impact of CVE-2026-3922 is substantial for organizations worldwide due to the ubiquity of Google Chrome as a primary web browser. Successful exploitation can lead to arbitrary code execution, allowing attackers to install malware, exfiltrate data, or disrupt services. This compromises confidentiality, integrity, and availability of affected systems. Organizations relying on Chrome for web access, especially those handling sensitive or regulated data, face increased risk of data breaches and operational disruption. The requirement for user interaction means phishing or drive-by download attacks could be vectors, increasing the threat surface. Enterprises with large user bases or those in sectors such as finance, healthcare, and government are particularly vulnerable. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as proof-of-concept exploits could emerge rapidly. Failure to patch promptly could lead to widespread exploitation, especially in environments where users frequently access untrusted web content.

Mitigation Recommendations

To mitigate CVE-2026-3922, organizations should immediately update all instances of Google Chrome to version 146.0.7680.71 or later, where the vulnerability is patched. Beyond patching, organizations should enforce strict browser update policies to ensure timely deployment of security fixes. Employing web filtering solutions to block access to known malicious sites can reduce exposure to crafted HTML pages exploiting this flaw. Implementing endpoint detection and response (EDR) tools can help identify suspicious browser behavior indicative of exploitation attempts. User education on the risks of interacting with untrusted websites and phishing awareness can reduce the likelihood of successful exploitation. For high-security environments, consider deploying browser isolation technologies to contain potential attacks. Monitoring threat intelligence feeds for emerging exploits related to this CVE is also recommended to adapt defenses proactively. Finally, organizations should audit and restrict browser extensions and plugins that could increase attack surface or interfere with security controls.

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-11T05:54:10.393Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b2c3542f860ef94391644e

Added to database: 3/12/2026, 1:44:52 PM

Last enriched: 3/12/2026, 1:59:38 PM

Last updated: 3/14/2026, 2:24:38 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