VulnerabilityPublished 20 Mar 2026

CVE-2026-4453: Google Chrome · Integer Overflow

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 146.0.7680.153 when convenient.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 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 31 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.153.

Affected software

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

AI-suggested

To mitigate CVE-2026-4453, organizations should immediately update all Mac-based Chrome browsers to version 146.0.7680.153 or later, where the vulnerability is patched. Enterprises should enforce automated update policies and verify compliance through endpoint management tools. Additionally, implement web filtering and content security policies to restrict access to untrusted or suspicious websites that could host malicious HTML content. Security awareness training should emphasize the risks of interacting with unknown links or web pages. Network monitoring should be enhanced to detect unusual outbound data flows that may indicate data exfiltration attempts. Consider deploying browser isolation technologies for high-risk users to contain potential exploitation. Finally, maintain an incident response plan that includes steps for handling potential data leakage incidents stemming from browser vulnerabilities.

Description

Integer overflow in Dawn in Google Chrome on Mac prior to 146.0.7680.153 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

Impact

The primary impact of CVE-2026-4453 is the unauthorized disclosure of sensitive information across web origins, violating the same-origin policy that underpins web security. This can lead to leakage of confidential user data such as authentication tokens, personal information, or other sensitive content accessible in the browser context. Organizations with employees or users on Mac systems running vulnerable Chrome versions are at risk of data breaches and privacy violations. The attack vector requires user interaction, which may limit mass exploitation but targeted spear-phishing or malicious web campaigns could be effective. The vulnerability undermines trust in web isolation mechanisms and could be leveraged as part of more complex attack chains. Although availability and integrity are not directly impacted, the confidentiality breach alone can have serious consequences including regulatory penalties, reputational damage, and potential lateral movement within corporate networks if sensitive credentials are exposed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats