Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. 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.

There are currently no reports of these vulnerabilities being exploited in the wild. 

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):

• Buffer overflow in ANGLE (CVE-2026-95350, CVE-2026-95281, CVE-2026-95284)
• Out of bounds write in GPU (CVE-2026-95357, CVE-2026-95322)
• Use after free in ServiceWorker (CVE-2026-95339)
• Use after free in Fullscreen (CVE-2026-95313)
• Buffer overflow in WebGL (CVE-2026-95349)
• Out of bounds write in WebGL (CVE-2026-95329)
• Use after free in WindowDialog (CVE-2026-95356)
• Use after free in AdFilter (CVE-2026-95310)
• Missing authorization in Extensions (CVE-2026-95301)
• UI misrepresentation in SecurityIndicators (CVE-2026-95291)
• Incorrect authorization in Navigation (CVE-2026-95355)
• Use after free in Aura (CVE-2026-95315)
• Use after free in Browser (CVE-2026-95298)
• Use after free in Chromecast (CVE-2026-95372)
• Uninitialized resource in GPU (CVE-2026-95324, CVE-2026-95293, CVE-2026-95359)
• Buffer overflow in Tint (CVE-2026-95283)
• Improper output encoding in DevTools (CVE-2026-95274)
• Use after free in Platform (CVE-2026-95282)
• Use after free in DevTools (CVE-2026-95373)
• Use after free in Views (CVE-2026-95277, CVE-2026-95351)
• Use after free in Bluetooth (CVE-2026-95348)
• Use after free in HID (CVE-2026-95335)
• Use after free in PDFium (CVE-2026-95338)
• Buffer overflow in Video (CVE-2026-95318)
• Type confusion in Bindings (CVE-2026-95286)
• Type confusion in IndexedDB (CVE-2026-95365)
• Use after free in WebAudio (CVE-2026-95343)
• Race condition in V8 (CVE-2026-95280)
• Out of bounds write in V8 (CVE-2026-95304)
• Type confusion in V8 (CVE-2026-95306, CVE-2026-95380)
• Use after free in GPU (CVE-2026-95299)
• Missing authorization in Navigation (CVE-2026-95287, CVE-2026-95320)
• Use of released resource in Core (CVE-2026-95366)
• Improper input validation in Auth (CVE-2026-95382)
• Improper input validation in Printing (CVE-2026-95381)
• Out of bounds write in ANGLE (CVE-2026-95331)
• Missing authorization in Contextual Tasks (CVE-2026-95297)
• Incorrect authorization in BrowserTag (CVE-2026-95375)
• Incorrect authorization in WebAPKs (CVE-2026-95302)
• Cross-site request forgery in DevTools (CVE-2026-95362)
• Inappropriate implementation in XML (CVE-2026-95369)
• Externally controlled reference in DevTools (CVE-2026-95376)
• UI misrepresentation in Browser (CVE-2026-95294)
• UI misrepresentation in Messages (CVE-2026-95337)
• UI misrepresentation in Chromoting (CVE-2026-95346, CVE-2026-95305)
• Incorrect authorization in MediaCapture (CVE-2026-95317)
• Use after free in Actor (CVE-2026-95345)
• Improper state validation in Downloads (CVE-2026-95330)
• Inappropriate implementation in NFC (CVE-2026-95370)
• Incomplete cleanup in SmartCard (CVE-2026-95303)
• Race condition in Editing (CVE-2026-95360)
• Information leak in Mobile (CVE-2026-95295)
• Improper input validation in Themes (CVE-2026-95276)
• Incorrect authorization in HID (CVE-2026-95314)
• Missing authorization in Views (CVE-2026-95371)
• Use after free in Bindings (CVE-2026-95353)
• UI misrepresentation in FileSystem (CVE-2026-95363)
• Improper input validation in Desktop (CVE-2026-95341)
• Use after free in Verifier (CVE-2026-95354)
• Race condition in Transactions Platform (CVE-2026-95384)
• Information leak in Transactions Platform (CVE-2026-95336)
• Missing authorization in NFC (CVE-2026-95290)
• Use after free in ANGLE (CVE-2026-95325)
• Incorrect reference resolution in MediaStream (CVE-2026-95275)
• Incorrect authorization in Network (CVE-2026-95374)
• Missing authorization in DevTools (CVE-2026-95300)
• UI misrepresentation in Payments (CVE-2026-95321)
• UI misrepresentation in Chromium (CVE-2026-95323)
• Use of uninitialized variable in Tint (CVE-2026-95332)
• Information leak in Passwords (CVE-2026-95312)
• Race condition in DevTools (CVE-2026-95344)
• Incorrect authorization in Scroll (CVE-2026-95289)
• Use after free in Updater (CVE-2026-95347)
• Free of non-heap memory in Fonts (CVE-2026-95311)
• Incorrect authorization in Mobile (CVE-2026-95358)
• Use after free in Metrics (CVE-2026-95333)
• UI misrepresentation in ExtensionsMenu (CVE-2026-95307)
• Missing authorization in WebView (CVE-2026-95285)
• Missing authorization in WakeLock (CVE-2026-95278)
• Information leak in Networking (CVE-2026-95327)
• Incorrect reference resolution in WebProtect (CVE-2026-95334)
• Integer overflow in Metrics (CVE-2026-95308)
• Incorrect authorization in Safebrowsing (CVE-2026-95292)
• Incorrect authorization in DevTools (CVE-2026-95352, CVE-2026-95368)
• UI misrepresentation in Omnibox (CVE-2026-95279)
• Information leak in DataTransfer (CVE-2026-95367)
• Inappropriate implementation in PlatformIntegration (CVE-2026-95385)
• Use after free in Printing (CVE-2026-95319)
• Incomplete cleanup in Bluetooth (CVE-2026-95326)
• UI misrepresentation in Mobile (CVE-2026-95309, CVE-2026-95288)
• Confused deputy in DevTools (CVE-2026-95361)
• Missing authorization in V8 (CVE-2026-95342)
• Missing authorization in Core (CVE-2026-95296)
• Unchecked return value in Performance (CVE-2026-95316)
• Confused deputy in Mobile (CVE-2026-95328)
• Incorrect authorization in PictureInPicture (CVE-2026-95340)
• Improper input validation in Passwords (CVE-2026-95364) 

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.