VulnerabilityPublished 24 Mar 2026Updated 25 Mar 2026

CVE-2026-4674: Google Chrome · Out-of-bounds Read

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 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

8.8High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% 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 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-4674, organizations should immediately update all instances of Google Chrome to version 146.0.7680.165 or later, where the vulnerability is patched. Automated patch management solutions should be employed to ensure timely deployment across all endpoints. Additionally, implement web content filtering to block access to untrusted or suspicious websites that could host malicious HTML content exploiting this vulnerability. Employ endpoint detection and response (EDR) tools to monitor for anomalous browser behavior indicative of exploitation attempts. Educate users about the risks of interacting with unknown or suspicious links and encourage cautious browsing habits. For high-security environments, consider deploying browser isolation technologies to contain potential exploitation within a controlled environment. Regularly review browser security settings and disable unnecessary plugins or extensions that could increase attack surface. Finally, maintain up-to-date threat intelligence feeds to stay informed about any emerging exploits targeting this vulnerability.

Description

CVE-2026-4674 is a high-severity out-of-bounds read vulnerability in the CSS processing component of Google Chrome versions prior to 146.0.7680.165. This flaw allows a remote attacker to craft a malicious HTML page that triggers out-of-bounds memory access, potentially leading to disclosure of sensitive information or further exploitation. The vulnerability requires user interaction, such as visiting a malicious webpage, and does not require prior authentication. Although no known exploits are currently reported in the wild, the vulnerability's high CVSS score of 8.8 reflects its serious impact on confidentiality, integrity, and availability. Organizations using affected Chrome versions are at risk, especially those with users frequently browsing untrusted websites. Immediate patching to version 146.

Impact

The impact of CVE-2026-4674 is substantial due to the widespread use of Google Chrome globally. Successful exploitation can lead to unauthorized disclosure of sensitive information from browser memory, potentially exposing user credentials, session tokens, or other confidential data. Furthermore, out-of-bounds memory access can be a stepping stone to remote code execution, allowing attackers to execute arbitrary code within the browser context, compromising system integrity and availability. This can result in browser crashes, data corruption, or persistent malware infections. Enterprises with employees accessing the internet via vulnerable Chrome versions are at risk of targeted attacks, especially in sectors handling sensitive data such as finance, healthcare, and government. The requirement for user interaction limits automated exploitation but does not eliminate risk, as phishing and drive-by download attacks remain effective vectors. The absence of known exploits in the wild currently reduces immediate risk but does not preclude future exploitation. Overall, the vulnerability poses a high risk to confidentiality, integrity, and availability of systems using affected Chrome versions.

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