VulnerabilityPublished 24 Mar 2026Updated 25 Mar 2026

CVE-2026-4675: 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.165 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.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 146.0.7680.165

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 24 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.165.

Affected software

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

AI-suggested

To mitigate CVE-2026-4675, organizations and users should immediately update Google Chrome to version 146.0.7680.165 or later, where the vulnerability is patched. Enterprises should enforce browser update policies and automate patch management to ensure timely deployment. Additionally, restricting access to untrusted or unknown websites can reduce exposure, as exploitation requires visiting a malicious page. Employing web content filtering and network security controls to block or monitor suspicious WebGL activity can provide additional defense layers. Security teams should monitor threat intelligence feeds for any emerging exploit attempts targeting this vulnerability. For high-security environments, consider disabling WebGL functionality temporarily until patches are applied. User education on avoiding suspicious links and websites also helps reduce risk. Finally, integrating browser security features such as sandboxing and enabling exploit mitigation technologies can limit the impact of potential attacks.

Description

CVE-2026-4675 is a high-severity heap buffer overflow vulnerability in the WebGL component of Google Chrome versions prior to 146.0.7680.165. It allows a remote attacker to trigger an out-of-bounds memory read by delivering a crafted HTML page, potentially leading to full compromise of confidentiality, integrity, and availability. Exploitation requires user interaction but no privileges or authentication. Although no known exploits are currently observed in the wild, the vulnerability's high CVSS score of 8.8 reflects its critical impact. This flaw affects a widely used browser, making it a significant risk for organizations globally. Mitigation involves promptly updating Chrome to version 146.

Impact

The impact of CVE-2026-4675 is significant due to the widespread use of Google Chrome as a primary web browser globally. Successful exploitation can lead to remote code execution, enabling attackers to take full control of the affected system under the context of the browser user. This compromises confidentiality by exposing sensitive data, integrity by allowing unauthorized code execution, and availability by causing browser or system crashes. Organizations relying on Chrome for daily operations, especially those handling sensitive information or operating in high-risk sectors such as finance, healthcare, and government, face elevated risks. The vulnerability could be exploited to deploy malware, conduct espionage, or disrupt services. Given the ease of exploitation (no privileges required and only user interaction), the threat surface is broad, affecting individual users, enterprises, and cloud environments where Chrome is used for web access. The absence of known exploits in the wild currently provides a window for proactive mitigation before active exploitation occurs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 20:29 UTC

Technical details

References

Community reviews

Related threats