Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows:

Tactic: Initial Access (TA0001):

Technique: Drive-By Compromise (T1189):

• Use after free in Ozone. (CVE-2026-11628)
• Use after free in Ozone. (CVE-2026-11629)
• Use after free in File Input. (CVE-2026-11630)
• Use after free in Aura. (CVE-2026-11631)
• Use after free in TabStrip. (CVE-2026-11632)
• Use after free in Bluetooth. (CVE-2026-11633)
• Use after free in Gamepad. (CVE-2026-11634)
• Use after free in Bluetooth. (CVE-2026-11635)
• Use after free in Autofill. (CVE-2026-11636)
• Use after free in Views. (CVE-2026-11637)
• Use after free in Printing. (CVE-2026-11638)
• Use after free in Compositing. (CVE-2026-11639)
• Integer overflow in libyuv. (CVE-2026-11640)
• Use after free in Bluetooth. (CVE-2026-11641)
• Use after free in Web Apps. (CVE-2026-11642)
• Use after free in Proxy. (CVE-2026-11643)
• Use after free in Views. (CVE-2026-11644)
• Out of bounds memory access in V8. (CVE-2026-11645)
• Use after free in ViewTransitions. (CVE-2026-11646)
• Use after free in Printing. (CVE-2026-11647)
• Use after free in FullScreen. (CVE-2026-11648)
• Use after free in V8. (CVE-2026-11649)
• Use after free in V8. (CVE-2026-11650)
• Use after free in Network. (CVE-2026-11651)
• Use after free in Extensions. (CVE-2026-11652)
• Insufficient validation of untrusted input in Extensions. (CVE-2026-11653)
• Use after free in CameraCapture. (CVE-2026-11654)
• Integer overflow in Media. (CVE-2026-11655)
• Use after free in ServiceWorker. (CVE-2026-11656)
• Use after free in Payments. (CVE-2026-11657)
• Insufficient validation of untrusted input in Extensions. (CVE-2026-11658)
• Insufficient validation of untrusted input in UI. (CVE-2026-11659)
• Insufficient validation of untrusted input in New Tab Page. (CVE-2026-11660)
• Use after free in Views. (CVE-2026-11661)
• Type Confusion in Bindings. (CVE-2026-11662)
• Use after free in Skia. (CVE-2026-11663)
• Use after free in Payments. (CVE-2026-11664)
• Out of bounds read in Dawn. (CVE-2026-11665)
• Insufficient validation of untrusted input in Input. (CVE-2026-11666)
• Out of bounds read in WebRTC. (CVE-2026-11667)
• Uninitialized Use in Codecs. (CVE-2026-11668)
• Integer overflow in Media. (CVE-2026-11669)
• Use after free in PDF. (CVE-2026-11670)
• Use after free in Navigation. (CVE-2026-11671)
• Out of bounds write in GPU. (CVE-2026-11672)
• Use after free in InterestGroups. (CVE-2026-11673)
• Use after free in Guest View. (CVE-2026-11674)
• Insufficient validation of untrusted input in Skia. (CVE-2026-11675)
• Insufficient validation of untrusted input in Dawn. (CVE-2026-11676)
• Race in Network. (CVE-2026-11677)
• Integer overflow in libyuv. (CVE-2026-11678)
• Use after free in Codecs. (CVE-2026-11679)
• Use after free in Media. (CVE-2026-11680)
• Use after free in Ozone. (CVE-2026-11681)
• Insufficient validation of untrusted input in Views. (CVE-2026-11682)
• Use after free in WebCodecs. (CVE-2026-11683)
• Insufficient policy enforcement in Network. (CVE-2026-11684)
• Insufficient data validation in MediaCapture. (CVE-2026-11685)
• Insufficient validation of untrusted input in Dawn. (CVE-2026-11686)
• Use after free in Dawn. (CVE-2026-11687)
• Object lifecycle issue in SVG. (CVE-2026-11688)
• Insufficient validation of untrusted input in Passwords. (CVE-2026-11689)
• Out of bounds read and write in Media. (CVE-2026-11690)
• Insufficient validation of untrusted input in New Tab Page. (CVE-2026-11691)
• Use after free in Read Anything. (CVE-2026-11692)
• Inappropriate implementation in Plugins. (CVE-2026-11693)
• Use after free in ServiceWorker. (CVE-2026-11694)
• Inappropriate implementation in Passwords. (CVE-2026-11695)
• Uninitialized Use in Video. (CVE-2026-11696)
• Insufficient validation of untrusted input in UI. (CVE-2026-11697)
• Use after free in Bluetooth. (CVE-2026-11698)
• Use after free in Bluetooth. (CVE-2026-11699)
• Use after free in Tracing. (CVE-2026-11700)
• Insufficient validation of untrusted input in Guest View. (CVE-2026-11701)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

We recommend the following actions be taken:

• Apply appropriate updates provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
• Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Safeguard 7.7: Remediate Detected Vulnerabilities:Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
• Safeguard 9.1: Ensure Use of Only Fully Supported Browsers and Email Clients:Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.

• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
• Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
• Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.

• Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)

• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
• Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

• Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
• Safeguard 9.2: Use DNS Filtering Services:Use DNS filtering services on all enterprise assets to block access to known malicious domains.
• Safeguard 9.3: Maintain and Enforce Network-Based URL Filters:Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
• Safeguard 9.6: Block Unnecessary File Types:Block unnecessary file types attempting to enter the enterprise’s email gateway.

• Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources. Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. (M1017: User Training)
• Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks:Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.