Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

MS-ISACEI-ISAC

MS-ISAC ADVISORY NUMBER:

2026-125

DATE(S) ISSUED:

11/06/2026

OVERVIEW:

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.

THREAT INTELLIGENCE:

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

SYSTEMS AFFECTED:

  • Chrome prior to 157.0.8103.38/.39 for Windows and Mac
  • Chrome prior to 157.0.8103.38 for Linux

RISK:

Government:
Large and medium government entitiesHIGH
Small governmentMEDIUM
Businesses:
Large and medium business entitiesHIGH
Small business entitiesMEDIUM
Home Users:
LOW

TECHNICAL SUMMARY:

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 Dawn (CVE-2026-121156, CVE-2026-121247)
  • Memory corruption in ANGLE (CVE-2026-121229)
  • Use after free in WebGL (CVE-2026-121246)
  • Use after free in Prerender (CVE-2026-121035)
  • Use after free in Geometry (CVE-2026-121203)
  • Use after free in Core (CVE-2026-121126)
  • Incorrect authorization in BackgroundFetch (CVE-2026-121107)
  • Out of bounds read in ANGLE (CVE-2026-121197)
  • Out of bounds read in Permissions (CVE-2026-121112)
  • Missing authorization in BackgroundFetch (CVE-2026-121174, CVE-2026-121102)
  • Improper state validation in GPU (CVE-2026-121098)
  • Memory corruption in GPU (CVE-2026-121074)
  • Uninitialized resource in WebGL (CVE-2026-121173, CVE-2026-121095)
  • Type confusion in CacheStorage (CVE-2026-121233)
  • Out of bounds read in Internals (CVE-2026-121140)
  • Incorrect authorization in FileSystem (CVE-2026-121071, CVE-2026-121104, CVE-2026-121060)
  • Uninitialized resource in Dawn (CVE-2026-121207)
  • Use after free in PictureInPicture (CVE-2026-121185)
  • Type confusion in PDFium (CVE-2026-121166)
  • Buffer overflow in Media (CVE-2026-121047, CVE-2026-121180)
  • Improper adherence to coding standards in XML (CVE-2026-121124)
  • Use after free in SVG (CVE-2026-121118)
  • Use after free in PerformanceAPIs (CVE-2026-121188)
  • Buffer overflow in PDFium (CVE-2026-121113)
  • Type confusion in V8 (CVE-2026-121082, CVE-2026-121228, CVE-2026-121210, CVE-2026-121057, CVE-2026-121094, CVE-2026-121226, CVE-2026-121068, CVE-2026-121078, CVE-2026-121221, CVE-2026-121218)
  • Use after free in Compositing (CVE-2026-121083)
  • Use after free in PDFium (CVE-2026-121179)
  • Use after free in Editing (CVE-2026-121181)
  • Use after free in Codecs (CVE-2026-121080)
  • Use after free in Layout (CVE-2026-121044)
  • UI misrepresentation in iOSWeb (CVE-2026-121051)
  • Information leak in Compositing (CVE-2026-121038)
  • Improper privilege management in Navigation (CVE-2026-121090)
  • Use after free in GPU (CVE-2026-121052)
  • Out of bounds write in ANGLE (CVE-2026-121037)
  • Buffer overflow in Skia (CVE-2026-121086)
  • Use after free in Mobile (CVE-2026-121131, CVE-2026-121077)
  • Improper input validation in Mobile (CVE-2026-121087)
  • Use after free in Aura (CVE-2026-121178)
  • Use after free in DOM (CVE-2026-121100, CVE-2026-121182)
  • Use after free in ANGLE (CVE-2026-121148)
  • Use after free in WebGPU (CVE-2026-121089)
  • Use after free in Extensions (CVE-2026-121250)
  • Out of bounds read in Skia (CVE-2026-121032, CVE-2026-121084, CVE-2026-121160)
  • Use after free in TabStrip (CVE-2026-121114, CVE-2026-121257)
  • Use after free in WebAudio (CVE-2026-121127)
  • Use after free in Animation (CVE-2026-121201)
  • Race condition in V8 (CVE-2026-121079, CVE-2026-121048)
  • Uninitialized resource in GPU (CVE-2026-121143, CVE-2026-121033)
  • Use after free in Printing (CVE-2026-121097)
  • Use after free in Passwords (CVE-2026-121214)
  • Incorrect reference resolution in Images (CVE-2026-121133)
  • Buffer overflow in ANGLE (CVE-2026-121249)
  • Uninitialized resource in Images (CVE-2026-121213)
  • Use after free in Navigation (CVE-2026-121241)
  • Security issue in Desktop (CVE-2026-121224)
  • Use after free in Paint (CVE-2026-121117)
  • Use after free in Canvas (CVE-2026-121123)
  • Use after free in Modularization (CVE-2026-121061)
  • Uninitialized resource in Skia (CVE-2026-121227, CVE-2026-121072)
  • Type confusion in DevTools (CVE-2026-121137)
  • Use after free in CSS (CVE-2026-121036)
  • Use after free in Views (CVE-2026-121034)
  • Out of bounds read in Media (CVE-2026-121208, CVE-2026-121184)
  • Use after free in WebRTC (CVE-2026-121129)
  • Use after free in PowerBookmarks (CVE-2026-121211)
  • Use after free in WebXR (CVE-2026-121076)
  • Use after free in Controls (CVE-2026-121119)
  • UI misrepresentation in FileAPI (CVE-2026-121244)
  • Improper input validation in WebPackaging (CVE-2026-121242)
  • Information leak in Network (CVE-2026-121105)
  • Improper state validation in FileSystem (CVE-2026-121237)
  • Improper input validation in Prerender (CVE-2026-121120)
  • Information leak in BackgroundFetch (CVE-2026-121161)
  • Incorrect authorization in API (CVE-2026-121062, CVE-2026-121248)
  • Missing authorization in PDF (CVE-2026-121031)
  • Incorrect authorization in CacheStorage (CVE-2026-121063)
  • Confused deputy in BackgroundFetch (CVE-2026-121108)
  • Missing authorization in Chromoting (CVE-2026-121199)
  • Information leak in PrivateTokens (CVE-2026-121099)
  • Privilege elevation in Mobile (CVE-2026-121196)
  • Incorrect authorization in Extensions (CVE-2026-121066, CVE-2026-121193, CVE-2026-121183, CVE-2026-121103)
  • Use of released resource in GPU (CVE-2026-121256)
  • Improper input validation in Shopping (CVE-2026-121115)
  • Privilege elevation in Contacts (CVE-2026-121234)
  • UI misrepresentation in PageInfo (CVE-2026-121177, CVE-2026-121121)
  • Information leak in Omnibox (CVE-2026-121106)
  • Incorrect reference resolution in DevTools (CVE-2026-121200)
  • Incorrect authorization in Proxy Auth (CVE-2026-121039)
  • UI misrepresentation in Prompts (CVE-2026-121122)
  • Integer overflow in GPU (CVE-2026-121219)
  • Incorrect authorization in Autofill AI (CVE-2026-121255)
  • Incorrect authorization in DevTools (CVE-2026-121231, CVE-2026-121030, CVE-2026-121065)
  • Missing authorization in DevTools (CVE-2026-121136, CVE-2026-121075, CVE-2026-121101, CVE-2026-121253, CVE-2026-121169)
  • Incorrect authorization in Core (CVE-2026-121040, CVE-2026-121220, CVE-2026-121212, CVE-2026-121252, CVE-2026-121232)
  • Improper resource control in WebCodecs (CVE-2026-121170)
  • Information leak in Core (CVE-2026-121059, CVE-2026-121239)
  • Improper input validation in Browser (CVE-2026-121163)
  • Missing authorization in PerformanceAPIs (CVE-2026-121088)
  • Information leak in Select (CVE-2026-121254)
  • Confused deputy in DevTools (CVE-2026-121171)
  • Missing authorization in WebView (CVE-2026-121116)
  • Observable discrepancy in Paint (CVE-2026-121187)
  • Information leak in V8 (CVE-2026-121132)
  • UI misrepresentation in PermissionElement (CVE-2026-121067)
  • Incomplete cleanup in V8 (CVE-2026-121096)
  • UI misrepresentation in Bluetooth (CVE-2026-121215)
  • Missing authorization in SiteIsolation (CVE-2026-121194)
  • Use after free in Autofill (CVE-2026-121202)
  • Use after free in WTF (CVE-2026-121070)
  • Incorrect authorization in Views (CVE-2026-121164)
  • Observable discrepancy in Media (CVE-2026-121223)
  • UI misrepresentation in Passwords (CVE-2026-121186, CVE-2026-121081)
  • Uninitialized resource in Media (CVE-2026-121176)
  • Use after free in Scheduling (CVE-2026-121128)
  • UI misrepresentation in UI (CVE-2026-121216)
  • Information leak in Paint (CVE-2026-121158, CVE-2026-121235)
  • UI misrepresentation in Shopping (CVE-2026-121110)
  • Incorrect authorization in Permissions (CVE-2026-121042, CVE-2026-121091, CVE-2026-121167, CVE-2026-121225)
  • Use after free in Source (CVE-2026-121238)
  • Race condition in Autofill (CVE-2026-121245)
  • Out of bounds read in V8 (CVE-2026-121049)
  • Security issue in Platform (CVE-2026-121135)
  • UI misrepresentation in Input (CVE-2026-121209)
  • Information loss in BackgroundFetch (CVE-2026-121134)
  • Use after free in Streaming (CVE-2026-121217)
  • Inadequate encryption strength in SSL (CVE-2026-121109)
  • Information leak in Frames (CVE-2026-121243)
  • UI misrepresentation in Transactions Platform (CVE-2026-121053)
  • UI misrepresentation in Extensions (CVE-2026-121190)
  • Information leak in ServiceWorker (CVE-2026-121125)
  • Incorrect authorization in WebAppInstalls (CVE-2026-121046)
  • Incorrect authorization in Forms (CVE-2026-121222)
  • Incorrect authorization in Chromoting (CVE-2026-121157)
  • Improper resource exposure in DevTools (CVE-2026-121168)
  • UI misrepresentation in Payments (CVE-2026-121043)
  • Incorrect authorization in HID (CVE-2026-121111)
  • Observable discrepancy in CORS (CVE-2026-121138)
  • Incomplete cleanup in DevTools (CVE-2026-121055, CVE-2026-121204)
  • Improper input validation in Network (CVE-2026-121236)
  • UI misrepresentation in Mobile (CVE-2026-121165)
  • Incorrect authorization in Isolated (CVE-2026-121172)
  • UI misrepresentation in Isolated (CVE-2026-121206)
  • Use after free in Browser (CVE-2026-121189)
  • Observable discrepancy in Forms (CVE-2026-121130)
  • Missing authorization in V8 (CVE-2026-121251)
  • Incorrect authorization in WebUI (CVE-2026-121085)
  • Incorrect authorization in History (CVE-2026-121159)
  • Incorrect authorization in CORS (CVE-2026-121205)
  • Race condition in Mobile (CVE-2026-121050)
  • Improper input validation in Variations (CVE-2026-121240)
  • Confused deputy in WebUI (CVE-2026-121198)
  • UI misrepresentation in Notifications (CVE-2026-121162)
  • UI misrepresentation in Browser (CVE-2026-121045)
  • Incorrect authorization in ORB (CVE-2026-121029)
  • Improper state validation in XML (CVE-2026-121054)
  • Improper resource exposure in ORB (CVE-2026-121175)
  • Uncontrolled recursion in SVG (CVE-2026-121092)
  • Use after free in Network (CVE-2026-121073)
  • Race condition in ANGLE (CVE-2026-121230)
  • Out of bounds read in Animation (CVE-2026-121093)
  • Missing authorization in Input (CVE-2026-121041)
  • Incorrect authorization in Network (CVE-2026-121142)
  • Use after free in Track (CVE-2026-121069)
  • Improper input validation in Performance (CVE-2026-121064)
  • Incorrect authorization in TrustedTypes (CVE-2026-121195)
  • Improper input validation in Editing (CVE-2026-121141)

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.

RECOMMENDATIONS:

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.


REFERENCES:

CVE

Get Email Updates When Cyber Threats Like This Arise

Subscribe to Advisories