VulnerabilityPublished 4 Mar 2026Updated 11 Mar 2026

CVE-2026-3538: Google Chrome · Integer Overflow

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 145.0.7632.159 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.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 145.0.7632.159

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 4 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 145.0.7632.159.

Affected software

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

AI-suggested

Immediately update Google Chrome to version 145.0.7632.159 or later, which contains the patch for this vulnerability.
Employ browser security best practices such as enabling automatic updates to ensure timely patch deployment.
Use web content filtering and URL reputation services to block access to known malicious sites that could host exploit pages.
Implement network-level protections such as intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous browser behavior or exploit attempts targeting Skia.
Enforce the principle of least privilege for browser processes and sandboxing to limit the impact of potential exploitation.
Educate users about the risks of interacting with untrusted web content and phishing attacks to reduce the likelihood of triggering the vulnerability.
Monitor security advisories and threat intelligence feeds for emerging exploit code or active campaigns targeting this vulnerability.
Consider deploying endpoint detection and response (EDR) solutions capable of detecting suspicious memory corruption or code execution patterns related to browser exploits.

Description

Integer overflow in Skia in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Critical)

Impact

The exploitation of CVE-2026-3538 can have severe consequences for organizations globally. Successful attacks can lead to arbitrary code execution within the browser context, enabling attackers to bypass security controls, steal sensitive information such as credentials or intellectual property, and potentially pivot to internal networks. The vulnerability compromises the confidentiality, integrity, and availability of affected systems. Given Chrome's widespread use as a primary web browser in enterprises, government agencies, and critical infrastructure, the risk of exploitation could disrupt business operations and damage reputations. The requirement for user interaction (visiting a malicious page) means phishing or drive-by download attacks could be vectors. Although no known exploits exist yet, the vulnerability's critical rating and ease of exploitation make it a prime target for attackers once exploit code becomes available. Organizations that delay patching face increased exposure to targeted attacks and widespread exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Mar 2026, 19:18 UTC

Technical details

References

Community reviews

Related threats