VulnerabilityPublished 24 Mar 2026Updated 25 Mar 2026

CVE-2026-4673: 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, 06:59 UTC

CVSS 3.1 base score

8.8High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% 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 29 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 Chrome and 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
Googlegoogle/chrome`pkg:deb/google/chrome`Other threats	Affected <146.0.7680.165	Fixed in 146.0.7680.165

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-4673, organizations should immediately update all instances of Google Chrome to version 146.0.7680.165 or later, where the vulnerability is patched. Since no direct patch links were provided, users should obtain updates through official Chrome update channels or enterprise deployment tools. Employ web content filtering and URL reputation services to block access to potentially malicious websites that could host exploit pages. Implement browser security policies that restrict or disable the WebAudio API in environments where audio processing is not required, reducing the attack surface. Use endpoint detection and response (EDR) solutions to monitor for anomalous browser behavior indicative of exploitation attempts. Educate users about the risks of visiting untrusted websites and the importance of prompt browser updates. Consider deploying browser isolation technologies to contain potential exploitation within sandboxed environments. Regularly audit browser versions across the organization to ensure compliance with security updates. Finally, maintain up-to-date backups and incident response plans to quickly recover from any successful attacks.

Description

CVE-2026-4673 is a high-severity heap buffer overflow vulnerability in the WebAudio component of Google Chrome versions prior to 146.0.7680.165. This flaw allows a remote attacker to execute an out-of-bounds memory write by delivering a 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 in the wild, the high CVSS score of 8.8 indicates significant risk. Organizations using vulnerable Chrome versions should prioritize patching to prevent exploitation.

Impact

The impact of CVE-2026-4673 is significant for organizations globally due to the ubiquity of Google Chrome as a primary web browser. Successful exploitation can lead to arbitrary code execution, allowing attackers to compromise user systems, steal sensitive data, or disrupt services. Confidentiality is at risk as attackers could access private information processed or stored by the browser. Integrity could be compromised by injecting malicious code or altering browser behavior. Availability may be affected if exploitation causes crashes or denial of service conditions. Given the remote exploitability and lack of authentication requirements, threat actors can target a wide range of users, including enterprise environments, government agencies, and critical infrastructure operators. The requirement for user interaction (visiting a malicious page) means phishing or drive-by download campaigns could be effective vectors. The absence of known exploits in the wild currently reduces immediate risk, but the high severity score and potential for rapid weaponization necessitate urgent mitigation. Organizations relying heavily on Chrome for daily operations face increased exposure, especially those with users who frequently access untrusted web content.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats