By vendor

Microsoft vulnerabilities

Known CVEs affecting Microsoft products, prioritized by severity, with SEC.co remediation and detection guidance.

899 published vulnerabilities · page 3 of 9

• CVE-2026-10909HIGH 8.3

  A use-after-free vulnerability in Google Chrome's Dawn graphics engine allows an attacker who has already compromised the browser's renderer process to escape the sandbox through a malicious webpage. This is a high-severity issue because it bridges two separate security boundaries—first gaining control within Chrome's renderer, then breaking out to execute arbitrary code on the underlying operating system.

• CVE-2026-10911HIGH 8.3

  CVE-2026-10911 is a sandbox escape vulnerability in Google Chrome that allows a remote attacker to break out of the browser's security sandbox if they have already compromised the renderer process. The attack requires crafted HTML content and user interaction, but once successful, it grants an attacker full system access. This is a chained attack scenario: an attacker must first compromise the renderer (the part of Chrome that displays web content) through a separate vulnerability, then use this flaw to escape the sandbox and gain control of the underlying system.

• CVE-2026-10917HIGH 8.3

  Google Chrome versions before 149.0.7827.53 contain a media handling flaw that allows an attacker who has already compromised the browser's renderer process to escape the sandbox and gain broader system access. The vulnerability requires user interaction (visiting a specially crafted webpage) but poses a significant risk because renderer compromises are common entry points in real attacks. Once inside the renderer, the flaw gives an attacker a path to elevated privileges on the underlying operating system.

• CVE-2026-10918HIGH 8.3

  A use-after-free vulnerability in Google Chrome's Viz component allows an attacker who has already compromised the browser's renderer process to potentially escape the sandbox and gain deeper system access. The attacker would need to trick a user into visiting a malicious webpage, but the actual exploitation requires prior renderer compromise, making this a multi-stage attack. While not currently known to be exploited in the wild, the vulnerability represents a meaningful privilege escalation path for sophisticated threat actors who have achieved initial browser process compromise.

• CVE-2026-10919HIGH 8.3

  A use-after-free bug in Chrome's ANGLE graphics library before version 149.0.7827.53 allows an attacker who already controls the browser's rendering process to break out of the sandbox and gain full system access. The attacker must trick a user into visiting a malicious webpage, but once the renderer is compromised, this flaw provides a path to escape Chrome's isolation boundaries.

• CVE-2026-10921HIGH 8.3

  A flaw in Google Chrome's graphics processing library (Dawn) could allow an attacker to break out of the browser's security sandbox if they've already compromised the rendering engine. The vulnerability stems from an integer overflow—a situation where a number calculation wraps around and produces an incorrect value—that could be triggered by a specially crafted webpage. While the attacker would need to have already gained access to the renderer process, successfully exploiting this could grant them the same privileges as the operating system user running Chrome, potentially leading to full system compromise.

• CVE-2026-10924HIGH 8.3

  A mathematical error in Chrome's Chromecast component allows an attacker who has already compromised Chrome's rendering engine to break out of the browser sandbox and gain full system access. The attacker needs to trick a user into visiting a malicious webpage while the renderer is already compromised. This is a serious vulnerability because sandbox escape means the attacker moves from limited browser permissions to unrestricted control of the entire device.

• CVE-2026-10927HIGH 8.3

  A memory reading flaw in Google Chrome's graphics component (Dawn) prior to version 149.0.7827.53 allows attackers who have already compromised the browser's renderer process to escape the sandbox through a specially crafted webpage. This is a two-stage attack: first an attacker must find a way into the renderer, then this vulnerability allows them to break out entirely.

• CVE-2026-10933HIGH 8.3

  A use-after-free vulnerability exists in Google Chrome's audio processing component on Windows systems. An attacker who has already compromised Chrome's renderer process could exploit this flaw through a specially crafted web page to escape the browser sandbox and gain higher privileges on the system. This requires an initial renderer compromise, but if successful, could lead to full system takeover.

• CVE-2026-10940HIGH 8.3

  A race condition vulnerability in Chrome's media codec handling allows an attacker who has already compromised Chrome's renderer process to escape the browser sandbox on Windows systems. The attacker would need to trick a user into visiting a specially crafted website, but once the renderer is compromised, this flaw could give the attacker full system-level access. Chrome versions before 149.0.7827.53 on Windows are affected.

• CVE-2026-10949HIGH 8.3

  A heap buffer overflow vulnerability in Google Chrome's video handling component allows an attacker who has already compromised Chrome's renderer process to escape the browser sandbox and gain system-level access. The attacker would need to craft a malicious HTML page to trigger the overflow, but exploitation requires the renderer to be already compromised—making this a post-compromise escape vector rather than a direct attack from an untrusted webpage. Chrome versions before 149.0.7827.53 are vulnerable on Windows, macOS, and Linux systems.

• CVE-2026-10960HIGH 8.3

  CVE-2026-10960 is a sandbox escape vulnerability in Google Chrome's video codec handling. An attacker who has already compromised Chrome's renderer process—the sandboxed component responsible for processing web content—can exploit an uninitialized variable in the codec logic to break out of the sandbox and gain full system access. The attack requires a crafted HTML page and user interaction, but once the renderer is compromised, the attacker can leverage this flaw to escalate to native code execution outside Chrome's security boundary.

• CVE-2026-10970HIGH 8.3

  Google Chrome versions prior to 149.0.7827.53 contain a vulnerability in how the browser validates input data related to Interest Groups—a feature used for targeted advertising. An attacker who has already compromised Chrome's renderer process (the part that executes web content) can exploit insufficient input validation to break out of the browser's sandbox—the security boundary designed to isolate web content from the rest of your system. This requires the attacker to first gain renderer access and trick a user into visiting a crafted webpage, but if successful, allows full control over the victim's machine.

• CVE-2026-11236HIGH 8.3

  Google Chrome versions before 149.0.7827.53 contain a flaw in how it enforces security policies for Web Bluetooth functionality. If an attacker has already compromised Chrome's rendering process (the part that runs web content), they could exploit this weakness to break out of Chrome's sandbox—the security boundary that isolates the browser from the rest of your system. An attacker would need to trick a user into visiting a specially crafted webpage while the renderer is already compromised. This is a chaining risk: the vulnerability itself requires a prior compromise, but once chained together, it enables full system access.

• CVE-2026-11256HIGH 8.3

  CVE-2026-11256 is a sandbox escape vulnerability in Google Chrome's GPU processing that affects versions prior to 149.0.7827.53. An attacker who has already compromised Chrome's renderer process can exploit an integer overflow in GPU code to break out of the browser sandbox and execute arbitrary code with higher privileges. The attack requires user interaction (visiting a malicious HTML page) and successful prior compromise of the renderer, making it a post-compromise escalation vector rather than a direct remote code execution path.

• CVE-2026-11631HIGH 8.3

  Google Chrome on Windows contains a use-after-free vulnerability in its Aura rendering subsystem that could allow an attacker to break out of the browser's sandbox. The flaw requires an attacker to first compromise the renderer process—typically through a separate vulnerability or exploit—and then use a malicious webpage to trigger memory corruption that escapes the sandbox. This is a post-exploitation technique rather than a direct entry point, but the consequence is severe: attackers could gain system-level access beyond Chrome's normal security boundaries.

• CVE-2026-11640HIGH 8.3

  A mathematical error in Google Chrome's image processing library (libyuv) can be exploited by attackers who have already compromised the browser's sandbox. By crafting a malicious HTML page, they can trigger an integer overflow that potentially breaks out of Chrome's security sandbox entirely, gaining full system access. This requires the attacker to have already penetrated the renderer process first, making it a second-stage attack rather than a direct entry point.

• CVE-2026-11642HIGH 8.3

  Google Chrome prior to version 149.0.7827.103 contains a use-after-free vulnerability in its web application handling that could allow a remote attacker to escape the browser's sandbox. The attack requires the attacker to first compromise the renderer process—a separate security boundary within Chrome—and then trick a user into visiting a malicious website. If successful, the attacker could potentially gain system-level access, though the vulnerability itself is triggered through browser interaction rather than automatic exploitation.

• CVE-2026-11652HIGH 8.3

  Google Chrome versions before 149.0.7827.103 contain a use-after-free vulnerability in its extension handling code that could allow an attacker to escape the browser sandbox. An attacker who has already compromised the Chrome renderer process—the isolated process that runs website code—could exploit this flaw by crafting a malicious HTML page to gain code execution outside the sandbox, potentially compromising the entire system. The vulnerability requires user interaction (such as visiting a malicious site) and a prior renderer compromise, making it a secondary exploitation vector rather than a direct entry point.

• CVE-2026-11656HIGH 8.3

  A use-after-free vulnerability exists in Google Chrome's ServiceWorker component that could allow attackers to escape the browser sandbox if they can trick a user into installing a malicious Chrome extension. The vulnerability affects Chrome versions before 149.0.7827.103 and requires user interaction to install the extension, but successful exploitation would grant an attacker access to the underlying system beyond Chrome's normal security boundaries.

• CVE-2026-11660HIGH 8.3

  A vulnerability in Google Chrome's New Tab Page feature allows an attacker who has already compromised Chrome's renderer process to escape the browser sandbox using a specially crafted HTML page. This is a critical privilege escalation risk because sandbox escapes can lead to full system compromise. The vulnerability affects Chrome versions before 149.0.7827.103 across Windows, macOS, and Linux.

• CVE-2026-11661HIGH 8.3

  A use-after-free flaw in Google Chrome's Views component on Windows allows a remote attacker to escape the browser's sandbox if the renderer process has already been compromised. The attacker would need to craft a malicious HTML page to trigger the vulnerability. This is a post-compromise escalation risk: while initial renderer compromise is required, successful exploitation grants code execution outside the sandbox, elevating the threat from contained to system-wide.

• CVE-2026-11663HIGH 8.3

  A use-after-free memory flaw exists in Google Chrome's Skia rendering engine. If an attacker first compromises Chrome's renderer process—the sandboxed component responsible for drawing web content—they can craft a malicious HTML page to trigger the vulnerability and break out of the sandbox, gaining full system access. This is a post-compromise attack chain: the renderer must already be compromised, but once it is, the attacker bypasses Chrome's key security boundary.

• CVE-2026-11679HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's codec handling on Windows systems. An attacker who has already compromised Chrome's renderer process—the sandboxed component that handles web content—could exploit this flaw via a malicious HTML page to break out of the sandbox and gain full system access. This requires the attacker to have already achieved renderer process compromise, making it a critical second-stage attack in a multi-stage exploitation chain.

• CVE-2026-11692HIGH 8.3

  A use-after-free vulnerability in Chrome's Read Anything feature allows an attacker who has already compromised the browser's renderer process to escape the sandbox and gain elevated system privileges. The attacker needs a user to open a malicious HTML page, but once triggered, the flaw breaks Chrome's security isolation and can lead to full system compromise. Google Chrome versions prior to 149.0.7827.103 are affected across Windows, macOS, and Linux.

• CVE-2026-11700HIGH 8.3

  A use-after-free flaw in Chrome's tracing component allows an attacker who has already compromised the renderer process to escape the browser sandbox through a specially crafted HTML page. While the attack requires the renderer to be compromised first, successful exploitation could give an attacker full system access beyond the browser's security boundaries.

• CVE-2026-12008HIGH 8.3

  A use-after-free vulnerability in Google Chrome's DigitalCredentials component allows attackers who have already compromised a browser's renderer process to potentially break out of Chrome's sandbox and gain system-level access. The flaw affects Chrome versions before 149.0.7827.115 and requires an attacker to serve a specially crafted webpage to trigger it. While the initial compromise of the renderer is a necessary prerequisite, successfully exploiting this vulnerability could give an attacker the ability to execute arbitrary code outside the browser's security boundaries.

• CVE-2026-12011HIGH 8.3

  A use-after-free flaw in Chrome's WebMIDI implementation allows attackers who have already broken into Chrome's rendering process to escape the browser sandbox and gain deeper system access on Windows. An attacker would need to trick a user into visiting a malicious webpage while having already compromised the renderer—a two-stage attack, but one that could lead to full system compromise if successful.

• CVE-2026-12014HIGH 8.3

  Google Chrome versions prior to 149.0.7827.115 contain a use-after-free memory vulnerability in the Cast feature that allows an attacker with access to the local network to escape the browser sandbox. The vulnerability requires specific conditions to trigger but, if successfully exploited, could grant an attacker code execution outside the browser's security boundaries. This is a local network attack vector, not a remote internet-wide threat, but poses significant risk in environments where untrusted devices share the same network segment.

• CVE-2026-12016HIGH 8.3

  Google Chrome versions before 149.0.7827.115 contain a vulnerability in the DevTools component that allows an attacker to escape the browser's sandbox. The attack requires two preconditions: the attacker must first compromise Chrome's renderer process (the component that executes web content), and the victim must interact with a specially crafted HTML page. Successfully exploiting this flaw could give an attacker full system access, bypassing Chrome's security isolation layer.

• CVE-2026-12029HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's video handling component on Windows systems. An attacker who has already compromised Chrome's renderer process—the sandboxed component that runs untrusted web content—could exploit this flaw through a specially crafted webpage to break out of the sandbox and gain full system access. This represents a critical step in a multi-stage attack chain, as the attacker must first compromise the renderer before leveraging this vulnerability for privilege escalation.

• CVE-2026-12031HIGH 8.3

  Google Chrome on Windows contains a flaw in how it handles Views that could allow an attacker with a compromised renderer process to escape the browser sandbox. An attacker would need to first compromise Chrome's renderer—typically through a separate browser vulnerability—then serve a specially crafted HTML page to trigger the sandbox escape. This is a serious chaining vulnerability because successful exploitation grants access to the operating system with the privileges of the user running Chrome.

• CVE-2026-12437HIGH 8.3

  A use-after-free vulnerability exists in Google Chrome's WebShare feature on Windows. If an attacker first compromises Chrome's renderer process (the sandboxed component that displays web content), they could exploit a flaw in how WebShare manages memory to escape the sandbox and gain full system access. This requires the attacker to have already compromised the renderer, meaning it's a post-compromise escalation rather than a primary attack vector.

• CVE-2026-12451HIGH 8.3

  Google Chrome versions before 149.0.7827.155 contain a use-after-free vulnerability in the DigitalCredentials component that can allow attackers who have already compromised the renderer process to break out of Chrome's sandbox and potentially execute arbitrary code on the host system. The vulnerability requires both renderer compromise and user interaction, making it a multi-stage attack chain. An attacker would first need to trick a user into visiting a malicious webpage, then leverage this flaw to escape Chrome's security boundaries.

• CVE-2026-12464HIGH 8.3

  A use-after-free memory vulnerability in Google Chrome's browser engine allows an attacker who has already compromised the renderer process to break out of the browser's sandbox and potentially execute arbitrary code with full system privileges. The vulnerability requires an attacker to first gain control of Chrome's renderer (the process that interprets web pages), then serve a specially crafted HTML page to trigger the memory corruption. This is a high-severity issue because sandbox escapes eliminate one of Chrome's primary security boundaries.

• CVE-2026-12465HIGH 8.3

  CVE-2026-12465 is a sandbox escape vulnerability in Google Chrome that stems from improper handling of object lifecycles in the Metrics component. An attacker who has already compromised Chrome's renderer process can exploit a crafted HTML page to break out of the browser sandbox and gain access to the underlying system. This is a post-compromise escalation path that requires the renderer to be compromised first, but once achieved, allows full system access.

• CVE-2026-12467HIGH 8.3

  Google Chrome versions before 149.0.7827.155 contain a use-after-free memory safety vulnerability in the Extensions system. An attacker who has already compromised a Chrome renderer process could exploit this flaw via a malicious HTML page to break out of Chrome's sandbox and gain full system access. The vulnerability requires user interaction (opening a crafted page) and successful renderer compromise, but once those conditions are met, the sandbox escape could be severe.

• CVE-2026-13025HIGH 8.3

  A race condition in Google Chrome's Developer Tools allows attackers who have already compromised Chrome's renderer process to break out of Chrome's security sandbox and gain access to the underlying operating system. The vulnerability requires the attacker to deliver a specially crafted webpage, but can lead to complete system compromise. This affects Chrome versions before 149.0.7827.197.

• CVE-2026-13281HIGH 8.3

  CVE-2026-13281 is a high-severity integer overflow vulnerability in the Mojo component of Google Chrome that could allow an attacker to escape the browser's sandbox if they first compromise the renderer process. An attacker would need to trick a user into opening a malicious file while controlling the renderer, creating a two-stage attack pathway. Successful exploitation could grant an attacker full system-level access beyond Chrome's security boundaries.

• CVE-2026-13801HIGH 8.3

  Google Chrome contains an integer overflow vulnerability in its Chromecast implementation that could allow an attacker to escape the browser's security sandbox. The flaw requires the attacker to first compromise the renderer process—the part of Chrome that executes web content—and then trick a user into visiting a specially crafted webpage. If successful, an attacker could break out of Chrome's sandbox isolation and gain access to the underlying operating system. This vulnerability affects Chrome versions before 150.0.7871.47 across Windows, macOS, and Linux.

• CVE-2026-13829HIGH 8.3

  A flaw in Google Chrome's Settings component on Windows allows an attacker who has already compromised Chrome's rendering engine to break out of the browser's security sandbox and gain broader system access. The vulnerability requires the attacker to first control the renderer process—typically through a separate browser exploit—and then use a specially crafted webpage to escape the sandbox. Chrome versions before 150.0.7871.47 are vulnerable.

• CVE-2026-15120HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's core rendering engine on Windows systems. An attacker who gains control of Chrome's renderer process—the isolated component that parses web content—can exploit this flaw via a malicious web page to escape the browser sandbox and execute arbitrary code with system privileges. The vulnerability requires both renderer compromise and user interaction, but the potential impact is severe because successful exploitation breaks Chrome's fundamental security isolation.

• CVE-2026-15122HIGH 8.3

  Google Chrome on Windows contains a vulnerability in its codec handling that could allow an attacker who has already compromised the browser's renderer process to break out of the sandbox and gain full system access. The vulnerability requires both a compromised renderer and user interaction with a malicious webpage, but if successfully exploited, it could lead to complete system compromise. Chrome versions prior to 150.0.7871.115 are affected.

• CVE-2026-50521HIGH 8.3

  Microsoft Edge (the Chromium-based version) contains a use-after-free memory flaw that allows an authenticated attacker to execute arbitrary code on a target system over the network without requiring user interaction. This is a serious vulnerability because it combines network-based attack delivery with high privileges for code execution, though it does require the attacker to already have valid credentials.

• CVE-2026-58284HIGH 8.3

  Microsoft Edge (Chromium-based) contains an authorization flaw that allows attackers to execute arbitrary code on affected systems over the network. The vulnerability requires user interaction—such as clicking a malicious link or opening a crafted document—but does not require the attacker to be authenticated. Once triggered, an attacker can gain the same privileges as the user running the browser, potentially leading to data theft, system compromise, or lateral movement.

• CVE-2026-58285HIGH 8.3

  Microsoft Edge (Chromium-based) contains a type confusion vulnerability that allows attackers to execute arbitrary code on a user's computer through network-based exploitation. The flaw occurs when the browser processes incompatible data types in memory, leading to a security boundary violation. Successful exploitation requires user interaction—typically visiting a malicious website or opening a crafted link—but does not require the attacker to have any elevated privileges or prior system access.

• CVE-2026-58287HIGH 8.3

  Microsoft Edge (Chromium-based) contains a use-after-free memory vulnerability that allows attackers to execute arbitrary code on a user's system. The flaw requires user interaction—such as visiting a malicious website or opening a crafted file—but once triggered, it can lead to complete system compromise. The vulnerability carries a HIGH severity rating and affects the integrity, confidentiality, and availability of affected systems.

• CVE-2026-58288HIGH 8.3

  Microsoft Edge (Chromium-based) contains a use-after-free memory vulnerability that allows an attacker to execute arbitrary code on a targeted user's machine. The vulnerability requires user interaction—such as visiting a malicious website or opening a crafted file—but does not require the attacker to have prior credentials or system access. Successful exploitation could grant the attacker full code execution capability with the privileges of the user running Edge.

• CVE-2026-58295HIGH 8.3

  Microsoft Edge (Chromium-based) contains a type confusion vulnerability that allows attackers to bypass security features through network requests without requiring user interaction or special privileges. The vulnerability receives a HIGH severity rating due to its network-exploitable nature and potential to undermine browser security controls.

• CVE-2026-9877HIGH 8.3

  A use-after-free memory vulnerability in the ANGLE graphics library affects Google Chrome versions before 148.0.7778.216. An attacker who has already compromised Chrome's renderer process can exploit this flaw through a specially crafted HTML page to escape the browser sandbox and gain unauthorized system access. While the attack requires an existing foothold in the renderer, the critical severity designation reflects the severe consequences of a successful sandbox escape.

• CVE-2026-9880HIGH 8.3

  Google Chrome versions before 148.0.7778.216 contain a flaw in WebGL input validation that allows an attacker who has already compromised the browser's renderer process to escape the browser sandbox and gain full system access. The vulnerability requires user interaction (clicking or otherwise engaging with a malicious page) but poses a critical risk once that initial renderer compromise occurs.

• CVE-2026-9890HIGH 8.3

  A use-after-free memory flaw exists in Google Chrome's Extended Reality (XR) implementation on Windows. An attacker who has already compromised Chrome's renderer process can exploit this defect through a malicious webpage to break out of the browser sandbox and gain system-level access. This is a privilege escalation attack that requires the renderer to be compromised first, making it part of a multi-stage exploitation chain.

• CVE-2026-9905HIGH 8.3

  A use-after-free vulnerability exists in Google Chrome's accessibility features on Windows. An attacker who has already compromised Chrome's renderer process can exploit this flaw through a specially crafted HTML page to break out of Chrome's sandbox and gain system-level access. This is a post-compromise risk: the attacker must first have control of the renderer, but if they do, this vulnerability provides a direct path to escape Chrome's security isolation and potentially take full control of your computer.

• CVE-2026-9924HIGH 8.3

  A flaw in the ANGLE graphics library (which Chrome uses to render graphics on Windows) can cause memory corruption when processing specially crafted web content. An attacker who has already compromised Chrome's sandboxed renderer process could exploit this to escape the sandbox and gain full system access. The vulnerability requires user interaction—the victim must open a malicious webpage—but once the renderer is compromised, the attacker has a path to execute code outside the sandbox.

• CVE-2026-9925HIGH 8.3

  A use-after-free flaw in ANGLE (the graphics abstraction layer used by Google Chrome) can allow an attacker to escape the browser sandbox if they first compromise the renderer process. The attacker would craft a malicious HTML page to trigger memory corruption that leads to code execution outside the sandbox boundary. This requires two conditions: initial renderer compromise and user interaction with the hostile page.

• CVE-2026-9926HIGH 8.3

  A memory error in Chrome's graphics processing component (ANGLE) could allow an attacker who has already compromised the renderer process to break out of the sandbox and access the wider system. The vulnerability requires the attacker to deliver a specially crafted webpage and the user to interact with it, but once triggered, it could lead to full system compromise. The issue affects Chrome versions prior to 148.0.7778.216.

• CVE-2026-9931HIGH 8.3

  A use-after-free memory flaw in Chrome's GPU component allows an attacker who has already compromised the browser's renderer process to break out of Chrome's sandbox and gain system-level access. The attacker would need to trick a user into visiting a malicious webpage while the renderer is already under attack. This is a post-compromise privilege escalation path rather than a direct remote attack vector.

• CVE-2026-9932HIGH 8.3

  A use-after-free vulnerability exists in the ANGLE graphics library within Google Chrome on Windows. An attacker who has already compromised Chrome's renderer process can exploit this flaw via a specially crafted HTML page to break out of Chrome's sandbox and gain full system access. This is a chained attack: the initial compromise must occur first, but once inside the renderer, the attacker gains significant additional capabilities.

• CVE-2026-9937HIGH 8.3

  A use-after-free flaw in Google Chrome's user interface on Windows allows an attacker who has already compromised Chrome's renderer process to escape the browser sandbox and gain system-level access. The attacker would need to craft a malicious HTML page to trigger the vulnerability. This is a critical privilege escalation path because sandbox escapes turn browser compromises into full system compromises.

• CVE-2026-9946HIGH 8.3

  A use-after-free vulnerability in Google Chrome's ANGLE graphics library could allow an attacker who has already compromised the browser's renderer process to break out of Chrome's security sandbox and execute code with system-level privileges. The flaw affects Chrome versions before 148.0.7778.216 and requires user interaction—typically visiting a malicious website—to trigger the vulnerability chain.

• CVE-2026-9949HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's Core component on Windows that could allow an attacker to escape the browser's sandbox. The vulnerability requires the attacker to have already compromised Chrome's renderer process and trick a user into visiting a malicious webpage. If successfully exploited, an attacker could gain the same privileges as the Windows user running Chrome, potentially compromising the entire system.

• CVE-2026-9951HIGH 8.3

  Google Chrome before version 148.0.7778.216 contains a use-after-free vulnerability in its user interface rendering engine. This flaw allows an attacker to craft a malicious HTML page that, when visited by a user, can trigger memory corruption. The vulnerability is particularly dangerous because it may enable attackers to break out of Chrome's sandbox—the security boundary that isolates the browser from the underlying operating system—potentially gaining direct access to system resources and user data. Exploitation requires user interaction (clicking or visiting a malicious site) and involves complex attack conditions, but the potential for sandbox escape elevates the risk significantly.

• CVE-2026-9966HIGH 8.3

  This vulnerability is an integer overflow flaw in how Google Chrome handles XML content on Windows systems. An attacker who has already compromised Chrome's rendering engine could craft a malicious HTML page to escape Chrome's security sandbox—the isolated environment that prevents malicious code from accessing your system directly. The vulnerability requires the attacker to have control of the renderer process first, and it requires user interaction (visiting a malicious page), but if exploited successfully, it could lead to complete system compromise.

• CVE-2026-9970HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's WebGL component that could allow an attacker to escape the browser sandbox. An attacker would first need to compromise Chrome's renderer process—typically through a separate exploit or social engineering—and then could use a specially crafted HTML page to gain unauthorized access outside the browser's security boundaries. This vulnerability affects Chrome versions before 148.0.7778.216 on Windows, macOS, and Linux systems.

• CVE-2026-9974HIGH 8.3

  CVE-2026-9974 is a memory safety bug in Google Chrome's GPU rendering component that can allow an attacker to escape the browser's sandbox if they first compromise the renderer process. The vulnerability stems from an out-of-bounds write operation, meaning the code writes data outside its intended memory boundaries. An attacker would need to trick a user into visiting a malicious webpage while already having control of Chrome's renderer, making this a secondary exploit that amplifies damage from other browser compromises.

• CVE-2026-9975HIGH 8.3

  A memory safety vulnerability in Google Chrome's ANGLE graphics library allows an attacker who has already compromised the browser's renderer process to break out of Chrome's sandbox and gain full system access. The flaw involves reading and writing memory beyond intended boundaries, creating a bridge from the restricted renderer environment to the host operating system. This requires the attacker to first successfully compromise the renderer (through a separate browser exploit or vulnerability) and then craft a malicious HTML page to trigger the escape.

• CVE-2026-9982HIGH 8.3

  CVE-2026-9982 is a sandbox escape vulnerability in Google Chrome's ANGLE graphics library. An attacker who has already compromised the browser's renderer process can exploit insufficient input validation to break out of the sandbox and gain system-level access. This requires an attacker to first deliver a malicious webpage that triggers the rendering flaw, making it a chained attack scenario rather than a one-step exploitation path.

• CVE-2026-9993HIGH 8.3

  A use-after-free memory vulnerability exists in Google Chrome's rendering engine that allows an attacker to escape the browser's sandbox if they have already compromised the renderer process. The vulnerability is triggered when a user opens a malicious PDF file. This is a critical threat because it could allow an attacker who has gained code execution within the browser to break out of Chrome's security boundaries and gain access to the underlying operating system.

• CVE-2026-9994HIGH 8.3

  A use-after-free vulnerability exists in Google Chrome's core rendering engine on Windows systems. An attacker who has already compromised the browser's renderer process can exploit this flaw through a specially crafted HTML page to escape the browser sandbox—breaking out of Chrome's security isolation layer. This means an attacker could potentially gain full system access from within the constrained renderer environment.

• CVE-2026-9997HIGH 8.3

  Google Chrome versions prior to 148.0.7778.216 contain a use-after-free vulnerability in the Input component that could allow an attacker to escape the browser's sandbox. The attack requires the attacker to have already compromised Chrome's renderer process and trick a user into visiting a malicious HTML page. If successful, the attacker could break out of the sandbox and gain access to the underlying operating system.

• CVE-2026-9998HIGH 8.3

  CVE-2026-9998 is a high-severity integer overflow vulnerability in Google Chrome's Skia graphics library that could allow an attacker to escape the browser's sandbox—a critical security boundary—if they first compromise Chrome's renderer process. The vulnerability requires a specially crafted HTML page and user interaction, making it a significant but not trivial threat. The issue affects Chrome versions before 148.0.7778.216.

• CVE-2026-44822HIGH 8.2

  Microsoft Office Excel contains an out-of-bounds read vulnerability that allows a remote attacker to extract sensitive information from a user's system without authentication or user interaction. The flaw affects multiple Microsoft Office products across different versions and deployment models. An attacker could exploit this by crafting a malicious Excel file or triggering the vulnerability over a network, potentially exposing confidential data.

• CVE-2026-45476HIGH 8.2

  A use-after-free flaw in the Linux MANA network driver used by Microsoft Azure allows a user with high-level system privileges to escape their confined context and gain full control over the system. Because the vulnerability requires the attacker to already have elevated privileges, the immediate attack surface is limited to administrative users or services running with high permissions—but successful exploitation would allow them to achieve complete system compromise.

• CVE-2026-47652HIGH 8.2

  A memory defect in Windows Hyper-V can allow someone with high-level system access to run malicious code on an affected machine. The flaw resides in how the hypervisor manages heap memory, leaving a window for buffer overflow attacks that bypass normal protections. This is a serious but constrained threat: exploitation requires administrative or hypervisor-level credentials, meaning it's not a remote vulnerability and the attacker must already have substantial control of the system.

• CVE-2026-57239HIGH 8.2

  A vulnerability in Foxit PDF Editor, Foxit PDF Reader, and Microsoft Windows allows low-privilege users to execute arbitrary code with system-level privileges. The flaw stems from these applications executing user-controlled files without proper validation, enabling attackers to escalate their privileges to NT AUTHORITY\SYSTEM. An attacker needs local access and user interaction to trigger the vulnerability, but once exploited, gains complete control over the affected system.

• CVE-2026-58525HIGH 8.2

  Microsoft Edge (Chromium-based) contains a flaw that allows attackers to bypass a security feature through network-based attack vectors. An attacker can exploit this weakness to gain unauthorized access to protected functionality, potentially compromising user confidentiality. The vulnerability requires user interaction to trigger, but once activated, impacts extend beyond the individual browser instance.

• CVE-2026-11011HIGH 8.1

  A flaw in Google Chrome's Password Manager allows an attacker who has already compromised the browser's renderer process to sidestep site isolation—a critical security boundary that prevents one website from accessing data belonging to another. By crafting a malicious HTML page, the attacker could potentially access sensitive information across different sites. This vulnerability affects Chrome versions before 149.0.7827.53 and requires the attacker to first gain control of the renderer process, which typically happens through a separate exploit or malicious website.

• CVE-2026-11015HIGH 8.1

  A memory reading flaw in Google Chrome's WebGPU component allows attackers to read data outside the intended memory boundaries when a user visits a specially crafted website. The vulnerability requires user interaction (visiting a malicious page) but does not require special privileges, and while the attacker cannot modify data or directly crash the browser, they can extract sensitive information from the process's memory—such as passwords, keys, or other confidential data stored there.

• CVE-2026-11111HIGH 8.1

  A memory reading vulnerability exists in Chrome's graphics engine (ANGLE) that allows attackers to access out-of-bounds data on a victim's system. An attacker could craft a malicious webpage that, when visited, leaks sensitive information from the browser's memory without modifying or corrupting system data. This affects Chrome versions prior to 149.0.7827.53. The vulnerability requires user interaction—a person must visit the malicious page—but once there, the attacker gains read access to protected memory regions.

• CVE-2026-11169HIGH 8.1

  Google Chrome versions before 149.0.7827.53 contain a flaw in how they process XML files that allows attackers to inject malicious scripts or HTML content into a webpage, even when normal security protections should prevent it. An attacker would need to trick a user into opening a specially crafted XML file, but once successful, the injected code can execute with the same privileges as the user, potentially stealing data or taking other harmful actions. The vulnerability affects Chrome on Windows, macOS, and Linux systems.

• CVE-2026-11185HIGH 8.1

  A use-after-free flaw in the V8 JavaScript engine affects Google Chrome versions before 149.0.7827.53. The vulnerability requires an attacker to trick a user into installing a malicious Chrome extension, which can then execute arbitrary code within the browser's sandbox. While the Chromium project rated this as Medium severity, the CVSS score of 8.1 reflects the high potential impact on confidentiality and integrity. This is a memory safety issue that leverages social engineering to gain code execution capabilities.

• CVE-2026-11643HIGH 8.1

  A use-after-free vulnerability exists in Google Chrome's Proxy component that could allow attackers to execute arbitrary code on victim machines through specially crafted network traffic. The flaw affects Chrome versions prior to 149.0.7827.103 and has been rated as Critical by the Chromium security team. While no active exploitation has been confirmed in the wild, the vulnerability's remote nature and code execution potential make it a significant threat requiring prompt patching.

• CVE-2026-11689HIGH 8.1

  A vulnerability in Google Chrome versions before 149.0.7827.103 allows an attacker who has already compromised Chrome's renderer process to break through site isolation—Chrome's security boundary that keeps websites from accessing each other's data. An attacker would need to trick a user into visiting a malicious webpage after the renderer is already compromised, but if successful, they could read or modify sensitive information across different websites.

• CVE-2026-11693HIGH 8.1

  Google Chrome versions before 149.0.7827.103 contain a flaw in how plugins are handled that allows a remote attacker to break through Chrome's site isolation security boundary. Site isolation is Chrome's defense mechanism that keeps different websites in separate processes to prevent one compromised site from accessing data from another. An attacker who has already compromised the renderer process—the part of Chrome that executes web pages—can craft a malicious HTML page to bypass this isolation, potentially gaining unauthorized access to sensitive data from other open websites or sessions.

• CVE-2026-12012HIGH 8.1

  Google Chrome contains a use-after-free flaw in its network handling code that could allow attackers on a privileged network position to corrupt Chrome's memory and potentially execute code. The vulnerability affects Chrome versions before 149.0.7827.115 and is rated High severity. An attacker would need both network access and the ability to intercept or manipulate traffic, but would not need user interaction to trigger the flaw.

• CVE-2026-13020HIGH 8.1

  Esri's Portal for ArcGIS contains a flaw in how it handles forgotten password requests. An attacker can exploit this weakness to take over user accounts without authorization. The vulnerability affects Portal for ArcGIS version 12.1 and earlier on Windows, Linux, and Kubernetes deployments. Organizations running these versions should prioritize patching or implementing the recommended email server configuration to enable secure self-service password recovery.

• CVE-2026-13774HIGH 8.1

  A use-after-free memory vulnerability exists in Google Chrome's extension handling mechanism. An attacker can exploit this by tricking a user into installing a malicious Chrome extension, which could then execute arbitrary code with the privileges of the Chrome browser. The vulnerability affects Chrome versions before 150.0.7871.47 and is rated as high-severity by CVSS standards, though Google classifies the underlying issue as critical from a Chromium perspective.

• CVE-2026-13787HIGH 8.1

  A use-after-free vulnerability exists in Google Chrome's Chromoting feature (remote desktop functionality) on Windows systems. The flaw allows an attacker to send specially crafted network traffic that causes Chrome to use memory that has already been freed, potentially leading to arbitrary code execution. This is a remote attack that requires no user interaction beyond having Chrome running, though specific network conditions must align for exploitation to succeed.

• CVE-2026-13791HIGH 8.1

  CVE-2026-13791 is a code execution vulnerability in Google Chrome's download handling system that affects versions prior to 150.0.7871.47. The flaw stems from insufficient validation of user-supplied input when processing malicious Chrome extensions. An attacker must first convince a user to install a specially crafted extension, but once installed, the extension can execute arbitrary code with the privileges of the Chrome process. This represents a post-installation code execution risk rather than a browser compromise via web browsing alone.

• CVE-2026-13799HIGH 8.1

  A use-after-free defect in Google Chrome's QUIC protocol implementation allows attackers to trigger memory corruption by sending specially crafted network packets. An attacker can exploit this remotely without user interaction or special privileges. While the vulnerability requires specific network conditions to trigger (reflected in the CVSS complexity score), successful exploitation could enable arbitrary code execution on affected systems.

• CVE-2026-14111HIGH 8.1

  A use-after-free vulnerability exists in Google Chrome's WebProtect component that could allow an attacker to run malicious code on a user's system. The vulnerability requires social engineering—specifically convincing a user to install a malicious browser extension—but once that hurdle is cleared, an attacker can execute arbitrary code with the privileges of the Chrome process. This affects Chrome versions prior to 150.0.7871.47 across Windows, macOS, and Linux systems.

• CVE-2026-14122HIGH 8.1

  A flaw in Google Chrome's WebAppInstalls feature on Windows allows attackers to read and modify files on a victim's computer by tricking them into visiting a malicious website. The vulnerability requires user interaction—a victim must click or interact with a crafted webpage—but once triggered, it can expose sensitive data or alter files without additional restrictions. Google has patched this in Chrome 150.0.7871.47 and later.

• CVE-2026-42835HIGH 8.1

  Microsoft Teams for Android contains an injection vulnerability that allows an authenticated attacker to extract sensitive information from the application. The flaw stems from improper handling of special characters in data passed to downstream components, creating a pathway for unauthorized data disclosure. An attacker must already have valid credentials to exploit this vulnerability, but once authenticated, they can access information without triggering user interaction or modifying data.

• CVE-2026-42974HIGH 8.1

  A flaw in Windows Performance Monitor allows an attacker to crash or take control of a system by sending specially crafted network requests. The vulnerability stems from how the Performance Monitor handles very large numbers, causing it to malfunction and execute unauthorized code. An attacker does not need valid credentials or user interaction to exploit this; they only need network access to the affected system.

• CVE-2026-42981HIGH 8.1

  Windows Performance Monitor contains an integer underflow vulnerability that allows attackers to execute arbitrary code on affected systems over a network without authentication. The flaw affects multiple versions of Windows 11 and Windows Server 2022/2025. While exploitation requires specific conditions (reflected in the CVSS complexity rating), successful attacks could grant an attacker full control of the compromised system.

• CVE-2026-42987HIGH 8.1

  CVE-2026-42987 is a use-after-free memory vulnerability in Windows Deployment Services (WDS) that allows an attacker to execute arbitrary code on vulnerable servers over the network without authentication or user interaction. The vulnerability affects multiple Windows Server versions and has a CVSS score of 8.1 (HIGH severity), indicating a significant risk to organizations relying on WDS for operating system deployment.

• CVE-2026-45503HIGH 8.1

  CVE-2026-45503 is a HIGH severity vulnerability in Microsoft Exchange Server that allows an already-authenticated attacker to access sensitive information over the network without user interaction. The flaw stems from improper authorization controls—meaning the server fails to properly verify what an authorized user should be allowed to see. An attacker with valid Exchange credentials can exploit this to read data they shouldn't have access to, such as emails, calendar entries, or other mailbox contents.

• CVE-2026-45599HIGH 8.1

  A use-after-free vulnerability in Windows UPnP (upnp.dll) allows an attacker to run unauthorized code on affected systems over the network without requiring user interaction or special privileges. The vulnerability affects multiple versions of Windows 10, Windows 11, and Windows Server, making it a broad concern for enterprises. While exploitation requires specific network conditions (reflected in the CVSS score of 8.1), successful attacks could lead to complete system compromise.

• CVE-2026-45635HIGH 8.1

  A type confusion vulnerability in Windows' Universal Plug and Play (UPnP) component allows attackers to execute code remotely on affected systems without authentication. The flaw stems from improper handling of incompatible data types in upnp.dll, which can be exploited over a network to gain full system compromise. This affects a broad range of Windows versions from Windows 10 through Windows 11, as well as Windows Server deployments.

• CVE-2026-47631HIGH 8.1

  Microsoft Exchange Server contains a cross-site scripting (XSS) vulnerability that could allow attackers to inject malicious scripts into web pages served by the Exchange interface. An attacker can trick users into visiting a crafted link, causing their browser to execute malicious code in the context of their Exchange session. This could lead to account compromise, email theft, or impersonation of the user to other Exchange recipients. The vulnerability requires user interaction (clicking a link) but does not require special privileges to exploit.