VulnerabilityPublished 11 Mar 2026Updated 13 Mar 2026

CVE-2026-3931: Google Chrome · Heap Buffer Overflow

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 146.0.7680.71 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 146.0.7680.71

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 146.0.7680.71.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=146.0.7680.71 <146.0.7680.71	Fixed in 146.0.7680.71

AI-suggested

Immediately update all Google Chrome installations to version 146.0.7680.71 or later, which contains the patch for this vulnerability.
Employ enterprise browser management tools to enforce timely updates and prevent use of vulnerable versions.
Use browser security features such as sandboxing, site isolation, and strict content security policies to limit the impact of potential exploitation.
Disable or restrict JavaScript execution in untrusted or unknown web contexts to reduce attack surface.
Educate users about the risks of visiting untrusted websites and clicking on suspicious links to reduce the likelihood of triggering the vulnerability.
Monitor network traffic and endpoint behavior for signs of exploitation attempts, including unusual memory access patterns or crashes in Chrome processes.
Consider deploying endpoint detection and response (EDR) solutions capable of detecting exploitation techniques related to memory corruption.
For high-security environments, consider using browser isolation technologies or alternative browsers with different rendering engines until patching is complete.
Regularly review and update incident response plans to include scenarios involving browser-based memory corruption exploits.
Coordinate with threat intelligence sources to stay informed about any emerging exploits targeting this vulnerability.

Description

CVE-2026-3931 is a high-severity heap buffer overflow vulnerability in the Skia graphics library used by Google Chrome versions prior to 146.0.7680.71. This flaw allows a remote attacker to trigger out-of-bounds memory access by delivering a specially crafted HTML page, potentially leading to arbitrary code execution. Exploitation requires user interaction, such as visiting a malicious webpage, but no prior authentication is needed. The vulnerability impacts confidentiality, integrity, and availability of affected systems. Although no known exploits are currently reported in the wild, the high CVSS score of 8.8 indicates significant risk. Organizations worldwide using vulnerable Chrome versions are at risk, especially those with high user exposure to web content.

Impact

The impact of CVE-2026-3931 is significant for organizations and individual users worldwide. Successful exploitation can lead to arbitrary code execution within the browser context, enabling attackers to install malware, steal sensitive data, or pivot to other parts of the network. Because Chrome is widely used across enterprises, government agencies, and consumers, the vulnerability poses a broad attack surface. Confidentiality is at risk due to potential data theft, integrity can be compromised by code injection or manipulation, and availability may be affected if attackers disrupt browser functionality or crash processes. The requirement for user interaction (visiting a malicious webpage) means phishing or drive-by download attacks are likely vectors. The vulnerability could be exploited in targeted attacks against high-value targets or in mass exploitation campaigns if weaponized. Organizations with large numbers of Chrome users, especially those in sectors with sensitive data such as finance, healthcare, and government, face elevated risk. The lack of known exploits in the wild currently provides a window for proactive patching and mitigation before widespread attacks occur.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:50 UTC

Technical details

References

Community reviews

Related threats