RCE
Monthly
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.
Chrome's Extensions subsystem prior to 153.0.8010.36 fails to correctly enforce security policies when inputs originate from a compromised renderer process (CWE-807), enabling a two-stage sandbox escape that results in arbitrary code execution outside the Chrome sandbox on the host OS. Exploitation chains a prior renderer compromise with social engineering to bypass Extensions-mediated policy decisions. No public exploit code exists and EPSS is low (0.30%, 22nd percentile), consistent with Chromium's internal 'Medium' severity rating despite the CVSS 8.3 score - reflecting the substantial pre-condition barrier.
Heap-based buffer overflow in the WebRTC component of Google Chrome prior to 153.0.8010.36 allows a remote unauthenticated attacker to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. The RCE is sandbox-confined (CVSS S:U), meaning a chained sandbox-escape exploit would be needed for full host-level compromise. No public exploit or active exploitation has been identified at time of analysis, and EPSS sits at a low 0.24% (15th percentile), consistent with Chromium's own 'Medium' severity designation despite the 8.8 CVSS base score.
Sandbox-escape remote code execution in Google Chrome's Extensions component (versions prior to 153.0.8010.36) lets a remote attacker potentially run arbitrary code outside the renderer sandbox by delivering crafted network traffic. The root cause is incorrect reference resolution (CWE-706), where a name or reference is resolved to the wrong target. Google has shipped a fix; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.20%).
Sandbox escape via confused deputy in Chrome's DataTransfer component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox by directing the victim to a crafted HTML page. Fixed in Chrome 153.0.8010.36, this is classified 'Medium' severity by the Chromium team despite the CVSS 8.3 score with full scope change (S:C, C:H/I:H/A:H), reflecting that renderer pre-compromise is required. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS is 0.25% (16th percentile).
Sandbox escape in Google Chrome's Extensions component (versions prior to 153.0.8010.36) permits an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via crafted network traffic. The missing authorization check (CWE-862) in the Extensions subsystem fails to enforce inter-process privilege boundaries, converting a renderer-level foothold into host-level code execution. No public exploit or active exploitation has been identified; EPSS sits at 0.19%, though SSVC rates the technical impact as 'total' given successful exploitation fully bypasses Chrome's sandbox isolation.
Sandbox escape via incorrect authorization in the WebView component of Google Chrome on Android (prior to 153.0.8010.36) allows a network-based attacker to execute arbitrary code outside the Chrome renderer sandbox. Exploitation is a two-stage process: the attacker must first compromise the renderer process, then leverage the CWE-863 authorization flaw in WebView to break out of the sandbox via a crafted HTML page. No public exploit or KEV listing has been identified at time of analysis; EPSS is low at 0.30%, consistent with the complexity barrier of requiring a prior renderer compromise.
Sandbox-escape via race condition in Google Chrome's Updater component on Windows allows a local, unprivileged attacker to execute arbitrary code outside the Chrome sandbox. Affected versions are all Chrome releases for Windows prior to 153.0.8010.36, fixed in the September 2026 stable channel update. No public exploit has been identified and EPSS sits at 0.10% (1st percentile), but successful exploitation yields full C:H/I:H/A:H impact beyond the sandbox boundary. Chromium's own rating of 'Medium' reflects the high attack complexity imposed by the race condition timing requirement.
Privilege elevation in Chrome's WebUI component prior to version 153.0.8010.36 enables sandbox escape and arbitrary code execution outside the browser sandbox when the renderer process has already been compromised. This is a second-stage, chained exploit: an attacker must first achieve renderer-level code execution (e.g., via a separate renderer bug) and then leverage this WebUI flaw (CWE-250 - execution with unnecessary privileges) to break out of the sandbox. No public exploit code has been identified and no CISA KEV listing exists; SSVC rates automatable exploitation as 'no', consistent with the multi-step chain requirement.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from incorrect reference resolution in the FileSystem component, letting a remote attacker who lures a victim into visiting a crafted HTML page run arbitrary code outside the renderer sandbox. Reported by Google's own Chrome team and patched in the 2026-09 stable-channel desktop update; no public exploit is identified and SSVC lists exploitation as none, with EPSS at a modest 0.32%. Note a signal conflict: Chromium rates this 'Medium' while the assigned CVSS is 9.6, and the description requires user interaction (social engineering), so real-world risk is lower than the raw score suggests.
Sandbox escape via improper input validation in Chrome's SiteIsolation component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox. Affected versions are all Chrome releases prior to 153.0.8010.36. Exploitation requires chaining this flaw with a separate renderer compromise - an attacker must first gain control of the renderer (typically via another renderer-targeted vulnerability), then use this SiteIsolation validation flaw to break out of the sandbox and execute code in a more privileged process context. No public exploit code or active exploitation has been identified at time of analysis.
Type confusion (CWE-843) in Chrome's XML processing component allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by enticing a target to visit a crafted HTML page. All Chrome desktop versions prior to 153.0.8010.36 are affected across Windows, macOS, and Linux. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the impact is further bounded by Chrome's sandbox architecture, which prevents direct OS-level code execution without a secondary sandbox-escape primitive.
Use-after-free in Chrome's Chromecast component allows remote attackers to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Affected are all Google Chrome releases prior to 153.0.8010.36 across desktop platforms. Exploitation is sandboxed - code execution is confined to the renderer process - but the C:H/I:H/A:H impact rating reflects full compromise of data accessible within that context. No active exploitation has been confirmed and no public proof-of-concept code is known at time of analysis.
Sandbox escape in Google Chrome's FileSystem component prior to 153.0.8010.36 stems from missing authorization checks (CWE-862), allowing arbitrary code execution outside the renderer sandbox. The attack is multi-stage: an attacker must first compromise the renderer process via a separate exploit, then serve a crafted HTML page using social engineering to trigger the authorization gap and escape the sandbox. No active exploitation is confirmed (not in CISA KEV; EPSS 0.34% at 27th percentile; SSVC exploitation: none), and the renderer pre-compromise requirement substantially limits real-world attack surface.
Out-of-bounds write in Chrome's V8 JavaScript engine allows remote attackers to execute arbitrary code within the renderer sandbox by directing a user to a crafted HTML page. All Google Chrome versions prior to 153.0.8010.36 are affected across desktop platforms. Impact is bounded by Chrome's renderer sandbox - an attacker achieves control over the renderer process and can access browser-stored data such as session cookies and saved credentials, but reaching the host OS would require a separately chained sandbox escape exploit. No public exploit identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the browser's Core component that a remote attacker can trigger through a maliciously crafted Chrome extension. Successful exploitation lets attacker-controlled code run outside the renderer sandbox with the browser process's privileges, but it requires convincing the victim to install or interact with the malicious extension (social engineering). There is no public exploit identified at time of analysis, EPSS is low (0.24%, 15th percentile), and CISA SSVC records exploitation as none, so the risk is high-impact but currently unproven in the wild.
Remote code execution in Google Chrome before 153.0.8010.36 stems from a use-after-free in the browser's Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Chromium rates the severity High, and the supplied CVSS is 9.6 reflecting the sandbox-escape scope change. EPSS is low (0.35%, 29th percentile) and no public exploit is identified at time of analysis.
Remote code execution inside the Chrome sandbox is possible in Google Chrome versions prior to 153.0.8010.36 via a use-after-free vulnerability in the V8 JavaScript engine, triggered by a specially crafted HTML page. An unauthenticated remote attacker who can lure a user to a malicious page can execute arbitrary code within the Chrome renderer process sandbox - a significant foothold even without a sandbox escape. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.21% reflects low observed exploitation activity, though V8 UAF primitives are historically attractive to threat actors.
Type confusion in V8 (CWE-843) in Google Chrome prior to 153.0.8010.36 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by delivering a crafted HTML page. All desktop Chrome installations on unpatched versions are affected, exploitable via drive-by browsing without any authentication or special privileges beyond convincing the victim to visit a malicious page. No public exploit or CISA KEV listing has been confirmed at time of analysis; SSVC rates technical impact as total but exploitation as none, consistent with a low EPSS of 0.23%.
Sandbox-escape code execution in Google Chrome's Printing subsystem (all versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a crafted HTML page, leveraging a use-after-free in the print handling path. This is a secondary exploit in a multi-stage chain: renderer compromise is a hard prerequisite, not something this bug alone provides. No public exploit code has been identified and CISA KEV does not list this vulnerability as actively exploited.
Sandbox-escaping remote code execution in Google Chrome's Payments component (versions prior to 153.0.8010.36) lets a remote attacker who successfully social-engineers a victim into visiting a crafted HTML page trigger a use-after-free and potentially run arbitrary code outside the renderer sandbox. Chromium rates the security severity 'High'; the supplied CVSS is 9.6 reflecting scope change and full CIA impact. No public exploit is identified at time of analysis and EPSS is low (0.26%, 17th percentile), and CISA SSVC records exploitation status as none.
Remote code execution in Google Chrome on macOS prior to 153.0.8010.36 stems from a use-after-free in the Payments component, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the browser sandbox. The provided CVSS vector (9.6) reflects a scope-changing sandbox escape requiring user interaction (a page visit), while Chromium rated the underlying bug 'High' rather than 'Critical'. A vendor patch is available; EPSS is low (0.30%, 22th percentile) and no public exploit is identified.
Sandbox-escape remote code execution in Google Chrome's Device component on macOS (versions prior to 153.0.8010.36) allows a remote attacker to potentially run arbitrary code outside the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) reported by Google's own Chrome team; Chromium assigned it 'High' severity while the CVSS base score is 9.6. No public exploit identified at time of analysis, and EPSS is low (0.26%).
Use-after-free in V8, Chrome's JavaScript engine, enables remote code execution within the browser's renderer sandbox when a victim visits a crafted HTML page. All Chrome releases prior to 153.0.8010.36 are affected across desktop platforms. No public exploit has been identified and EPSS sits at 0.21% (12th percentile), but SSVC rates the technical impact as total, and the Chromium security team classified this as High severity.
Use-after-free in Chrome's WebPackaging component enables full sandbox escape to arbitrary code execution for attackers who have already established a foothold in the renderer process. All Chrome desktop releases prior to 153.0.8010.36 are affected. No public exploit code has been identified and EPSS is low (0.34%), but the scope-changed CVSS vector (S:C, C:H/I:H/A:H) confirms that successful exploitation fully escapes Chrome's multi-process sandbox, translating a renderer compromise into OS-level code execution.
Use-after-free in Chrome's Input component enables in-sandbox remote code execution against all Chrome versions prior to 153.0.8010.36. The vulnerability is triggered when a victim visits a crafted HTML page, requiring no authentication and no special configuration - only a single browse action. Google has rated this High severity, the patch is available in 153.0.8010.36, and no public exploit has been identified at time of analysis, with EPSS at 0.21%.
Use-after-free in Chrome's Platform component (all versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a crafted HTML page. The Chromium team rated this 'High' severity - consistent with the CVSS 8.8 score and distinguishing it from Critical-rated full sandbox-escape vulnerabilities addressed in the same release cycle. No public exploit code has been identified, and the EPSS score of 0.21% (12th percentile) reflects limited observed exploitation activity at this time; no CISA KEV listing exists.
DevTools injection (CWE-74) in Google Chrome prior to 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to escape the Chromium sandbox and execute arbitrary code on the host system via a crafted HTML page. Chromium rated this 'High' severity; the CVSS 3.1 score of 8.3 (AC:H/S:C) accurately reflects the elevated complexity imposed by the prerequisite renderer compromise and the full scope-change impact. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.25% (16th percentile) confirms low current exploitation probability.
Sandbox-escaping remote code execution in Google Chrome before 153.0.8010.36 stems from improper array-index validation (CWE-129) in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can potentially corrupt memory and execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; no public exploit is identified at time of analysis and EPSS is low (0.21%).
Remote code execution outside the browser sandbox affects Google Chrome versions prior to 153.0.8010.36 through a use-after-free flaw in the Web Authentication (WebAuthn) component. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code with the privileges of the browser process, escaping the renderer sandbox (scope change). No public exploit has been identified at time of analysis and EPSS is low (0.34%), but the sandbox-escape RCE nature and Chrome's enormous install base make prompt patching important.
Remote code execution in Google Chrome's ANGLE graphics component on Windows (versions prior to 153.0.8010.36) allows a remote attacker to trigger an out-of-bounds write and potentially execute arbitrary code outside the browser sandbox via a crafted HTML page. Rated Chromium 'High' with a CVSS of 9.6 reflecting a scope-changing sandbox escape, though exploitation requires the victim to load malicious web content. No public exploit identified at time of analysis, and EPSS is low (0.21%), consistent with CISA SSVC scoring exploitation as 'none'.
Out-of-bounds read in ANGLE, Chrome's cross-platform graphics abstraction layer, enables sandbox escape and potential remote code execution on the host system for Chrome versions prior to 153.0.8010.36. This is a staged, second-phase exploit: an attacker must first compromise the renderer process through a separate vulnerability before leveraging this ANGLE flaw to break out of Chrome's sandbox via a crafted HTML page. No public exploit has been identified and no CISA KEV listing exists; EPSS at 0.21% (12th percentile) reflects minimal observed exploitation activity at time of analysis.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a heap buffer overflow in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can corrupt heap memory and execute arbitrary code outside the renderer sandbox, gaining full compromise of the host. No public exploit is identified at time of analysis and EPSS is low (0.33%), but the sandbox-escape scope and Chrome's near-universal footprint make prompt patching essential.
Out-of-bounds read in the WebGL component of Google Chrome before 153.0.8010.36 lets a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the browser sandbox. Chromium rates the security severity as High, and a vendor patch is available; no public exploit has been identified and CISA SSVC records exploitation as none, with EPSS at a low 0.28% (20th percentile).
Use-after-free in Chrome's Views UI framework enables local attackers to escape the browser sandbox and execute arbitrary code at browser-process privilege level. The vulnerability affects all Google Chrome desktop versions prior to 153.0.8010.36. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects low near-term exploitation probability.
Sandbox-escape remote code execution in Google Chrome on Android (versions prior to 153.0.8010.36) stems from a use-after-free in Dawn, Chromium's WebGPU implementation. A remote attacker who lures a victim to a crafted HTML page can trigger the freed-object reuse to execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; there is no public exploit or CISA KEV listing, and EPSS is low (0.30%), indicating no evidence of active or widespread exploitation at time of analysis.
Sandbox-escape remote code execution in Google Chrome (Chromium-based desktop) before 153.0.8010.36 stems from an incorrect authorization flaw in the DevTools component. A remote attacker who lures a victim to a crafted HTML page can potentially execute arbitrary code outside the renderer sandbox, achieving full compromise of the browser process. No public exploit identified at time of analysis; EPSS is low (0.21%, 11th percentile) and the issue is not in CISA KEV, but Google rates the Chromium security severity as High.
Sandbox-escape code execution via a race condition in the Google Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox. Affected builds are all Chrome versions prior to 153.0.8010.36 on Windows. The Chrome Updater's elevated-privilege execution context makes winning the race condition particularly impactful, as successful exploitation bypasses sandbox containment entirely.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local unprivileged attacker to execute arbitrary code outside the Chrome renderer sandbox by exploiting a race condition. All Chrome for Windows releases prior to 153.0.8010.36 are affected. No public exploit has been identified at time of analysis; EPSS places exploitation probability at the 3rd percentile, though SSVC rates technical impact as 'total,' reflecting full system compromise potential if the race condition is successfully won.
Use-after-free in Google Chrome's Core component on Windows prior to 153.0.8010.36 enables a renderer-compromised attacker to escape the browser sandbox and execute arbitrary code on the host OS. The vulnerability is platform-specific to Windows and functions as the second stage of a chained exploit: an attacker must first achieve renderer-level compromise before triggering this UAF to pivot into the privileged browser process. No public exploit code or active exploitation has been identified at time of analysis; vendor patch 153.0.8010.36 is available.
Use-after-free in Chrome's Receiver component allows an adjacent, unauthenticated attacker to execute arbitrary code outside the renderer sandbox via crafted network traffic, affecting all Chrome versions prior to 153.0.8010.36. The scope change in the CVSS vector confirms this is a full sandbox escape - successful exploitation yields OS-level code execution on the victim machine without requiring any user interaction. No public exploit has been identified at time of analysis, and EPSS at 0.13% (3rd percentile) indicates low observed exploitation activity.
Sandbox-escape remote code execution in Google Chrome's Views UI framework prior to 153.0.8010.36 allows a local attacker to execute arbitrary code outside the browser sandbox by inducing a specific UI interaction that triggers a use-after-free condition. The CVSS scope change (S:C) confirms the vulnerability crosses the renderer sandbox boundary into the broader OS context, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified at time of analysis; EPSS of 0.20% (10th percentile) reflects low automated exploitation probability, though sandbox escapes are high-value for privilege escalation chains.
Out-of-bounds read in Google Chrome's Media component (versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a specially crafted HTML page. The vulnerability stems from improper bounds checking during media processing, allowing a remote attacker to read memory beyond intended buffer limits and leverage the resulting data to achieve arbitrary code execution. No public exploit has been identified at time of analysis and EPSS is low (0.35%), but the attack surface is broad given Chrome's ubiquity.
Memory corruption in the Codecs component of Google Chrome prior to 153.0.8010.36 enables remote unauthenticated attackers to execute arbitrary code inside the browser sandbox by delivering a crafted HTML page containing malformed media content. The flaw is classified CWE-119 (improper bounds restriction), rated 'High' by Chromium Security, and carries a CVSS 8.8 base score with a network attack vector requiring only passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS stands at a low 0.35% (29th percentile), indicating theoretical rather than observed exploitation.
Double-free memory corruption in PDFium (Chrome's PDF rendering engine) on Windows allows remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF file. Affected versions are all Chrome releases on Windows prior to 153.0.8010.36, where CWE-415 double-free in the PDFium component enables an attacker-controlled allocation state. No public exploit or CISA KEV listing is confirmed at time of analysis, and EPSS remains low at 0.20% (10th percentile), suggesting exploitation is not yet widespread despite the network-reachable vector.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a use-after-free in ANGLE, Chrome's graphics abstraction layer that translates OpenGL ES calls to Direct3D. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code outside the browser sandbox, giving full compromise of the renderer host process. No public exploit identified at time of analysis, and EPSS is modest (0.35%), but the sandbox-escape impact and one-click delivery make this a high-priority browser patch.
Use-after-free in Chrome's Cast (Chromecast streaming) component allows an adjacent unauthenticated attacker to potentially escape the browser sandbox and execute arbitrary code by delivering crafted network traffic over a local or Wi-Fi network. All Chrome desktop versions prior to 153.0.8010.36 are affected, with Chromium rating this Critical due to the full-CIA, scope-changed impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.17% (6th percentile) indicates minimal observed exploitation activity despite the high severity classification.
Remote code execution in Google Chrome prior to 153.0.8010.36 allows a remote attacker to escape the renderer sandbox and run arbitrary code on the host by luring a victim to a crafted HTML page that triggers a heap buffer overflow in the WebGL implementation. Chromium rates this Critical and the CVSS 9.6 score reflects a scope-changing sandbox escape; no public exploit is identified at time of analysis, and EPSS is low at 0.29% (21st percentile). Patched in the September 2026 stable-channel desktop release.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 arises from an out-of-bounds write in the WebGL graphics subsystem, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the renderer sandbox. Rated Critical by Chromium and CVSS 9.6, the scope-changed vector reflects a full sandbox escape. No public exploit is identified at time of analysis and EPSS is low (0.39%), but WebGL memory-corruption bugs are historically high-value targets.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 stems from a use-after-free in the WebGL implementation that a remote attacker can trigger with a crafted HTML page to execute arbitrary code outside the browser sandbox. Chromium rates this Critical and the CVSS is 9.6, reflecting a full renderer-to-sandbox-escape chain requiring only that a victim visit a malicious page. No public exploit is identified at time of analysis and EPSS is low (0.36%), but the sandbox-escape impact makes it a priority patch.
Remote code execution in Google Chrome desktop prior to 153.0.8010.36 arises from a use-after-free in the WebGL implementation, allowing a remote attacker to run arbitrary code outside the browser sandbox by luring a victim to a crafted HTML page. Google rates the Chromium severity as Critical and the CVSS is 9.6, reflecting a full renderer-to-host sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.28% (20th percentile).
Arbitrary code execution in Actions Semiconductor's Tool - Media Player Utilities v4.46 lets a physically proximate attacker run code on a host by abusing the Production.dll and RdiskUpgrade.exe firmware/disk-upgrade components (CWE-94 code injection). The flaw affects this specific flashing/production utility bundled with Actions Semiconductor media-player SoC toolchains. SSVC rates technical impact as total with a public proof-of-concept, but EPSS is only 0.17% (6th percentile), and the required physical/local proximity sharply limits real-world reach.
Code injection in n8n's legacy expression engine allows an authenticated user to replace the mutable global JSON.stringify function within expression evaluation, causing subsequent code-generation paths to embed and execute attacker-controlled JavaScript. Affected are all n8n versions prior to 1.123.76 (v1 branch), 2.37.7, and 2.38.2. The vulnerability is confined to the legacy expression engine (isolated-vm-bridge.ts and ExpressionBuilder.ts); the vm expression engine is unaffected. No public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in n8n workflow automation platform prior to versions 1.123.76, 2.37.7, and 2.38.2 is achievable by any authenticated user who can author workflow expressions. The root cause is a sandbox escape in the PrototypeSanitizer AST hook: because the sanitizer references itself via dynamically scoped `this`, a crafted class field named `__sanitize` rebinds the sanitizer function, after which the expression freely invokes the JavaScript `Function()` constructor and executes arbitrary Node.js code on the backend. No public exploit has been identified at time of analysis, but the Function constructor escape technique is well-documented in the JavaScript security research community, lowering the barrier to independent rediscovery.
Remote code execution in Apache Impala 2.7.0 through 4.5.1 allows an authorized user with table-creation and remote-storage upload privileges to load and execute arbitrary Java classes on Impala daemon nodes by exploiting insufficient authorization controls over External Data Source tables. The vulnerability abuses Impala's legitimate extensibility feature - Data Source tables - which permits custom Java class loading from remote storage; insufficient authorization checks mean any user holding those two combined privileges can weaponize the feature for server-side code execution. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; upgrade to 4.5.2 is the vendor-confirmed fix.
Local privilege escalation in Auth0 AD/LDAP Connector versions up to and including 6.5.0 allows a low-privileged local user to modify the connector's configuration file due to improper permission handling during service startup processing. When the connector service restarts - whether scheduled, OS-triggered, or manually - the tampered configuration value is evaluated, resulting in code execution with the privileges of the service account running the connector. No public exploit code has been identified at time of analysis, but the straightforward local exploitation path (AC:L) and high impact to a service that often holds privileged Active Directory credentials make this a meaningful risk in environments running on-premise Auth0 connector deployments.
Heap-based buffer overflow in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution at current-user privilege level when a victim opens a crafted PDF or supported file format. Affected versions span Acrobat Reader ≤26.002.21900 and Acrobat 2024 ≤24.001.30383 across all supported platforms, as documented in Adobe advisory APSB26-141. No public exploit code or active exploitation in the wild has been identified at the time of this analysis, but Adobe Acrobat's ubiquity in enterprise document workflows makes this a credible phishing or spear-phishing vehicle.
Use-After-Free in Adobe Acrobat Reader and Adobe Acrobat allows arbitrary code execution in the security context of the current user upon opening a specially crafted PDF file. Affected versions span Acrobat Reader up to 26.002.21900 and Acrobat 2024 up to 24.001.30383, as documented in Adobe advisory APSB26-141. No public exploit identified at time of analysis, but the file-delivery attack vector makes this a realistic phishing and drive-by-download threat given Acrobat Reader's ubiquity as an enterprise PDF handler.
Use After Free in Adobe Acrobat Reader and Acrobat 2024 allows arbitrary code execution in the context of the current user when a victim opens a crafted malicious document. Affected across both the continuous track (≤26.002.21900) and the classic 2024 track (≤24.001.30383), this is a memory corruption vulnerability rooted in improper object lifecycle management within Acrobat's rendering engine. No public exploit code or CISA KEV listing has been identified at time of analysis, but the file-open attack surface and high impact make this a credible phishing or watering-hole delivery risk.
Use-after-free (UAF) in Adobe Acrobat Reader allows arbitrary code execution in the context of the authenticated local user when a victim opens a specially crafted malicious PDF or document file. Affected versions span Acrobat 2024 (≤24.001.30383) and both Acrobat and Acrobat Reader (≤26.002.21900), making the exposure broad across the current release track. No public exploit or active exploitation has been confirmed at time of analysis, but the file-based delivery vector makes this class of vulnerability routinely weaponized via phishing campaigns.
Integer overflow in Adobe Acrobat Reader and Acrobat (all editions through 26.002.21900) and Acrobat 2024 (through 24.001.30383) enables arbitrary code execution within the context of the victim's user account. The flaw is triggered when a user opens a specially crafted PDF file, making social engineering the primary delivery mechanism. No public exploit code or active exploitation has been identified at time of analysis, but the high CIA impact and wide deployment footprint make patching a priority.
Use-after-free (CWE-416) in Adobe Acrobat Reader enables arbitrary code execution in the context of the logged-in user when a victim opens a specially crafted PDF file. Affected versions include Acrobat Reader and Adobe Acrobat up to 26.002.21900 and Acrobat 2024 up to 24.001.30383, as documented in Adobe advisory APSB26-141. No public exploit code or active exploitation has been identified at time of analysis, but the ubiquity of Acrobat Reader across enterprise environments and the reliable code-execution impact make patching a high priority.
Use After Free in Adobe Acrobat Reader allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious document. Affected versions span both the continuous-track Acrobat/Acrobat Reader (≤26.002.21900) and the Acrobat 2024 classic track (≤24.001.30383). No public exploit or CISA KEV listing is identified at time of analysis, but the combination of a widely deployed document reader, file-open delivery vector, and full C/I/A impact makes this a high-priority patching target for enterprise environments.
Out-of-bounds write in Adobe Acrobat Reader and Acrobat allows arbitrary code execution in the context of the opening user when a victim opens a specially crafted malicious file. All versions of Acrobat Reader and Adobe Acrobat through 26.002.21900, and Acrobat 2024 through 24.001.30383, are affected. No public exploit code or CISA KEV listing has been identified at time of analysis, but the file-based delivery mechanism and full C:H/I:H/A:H impact make this a material risk for organizations with unpatched deployments.
Out-of-bounds write in Adobe Acrobat and Acrobat Reader allows arbitrary code execution in the current user's context when a victim opens a specially crafted file. Affected are Acrobat 2024 versions through 24.001.30383 and Adobe Acrobat/Acrobat Reader through 26.002.21900, per Adobe APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, though the ubiquity of Acrobat as an attack surface and the RCE-grade impact make this a priority patch.
Out-of-bounds write in Adobe Acrobat Reader and Acrobat (Continuous track through 26.002.21900; Classic 2024 track through 24.001.30383) enables arbitrary code execution in the context of the victim user. The CWE-787 memory corruption flaw is triggered when a specially crafted document is opened, placing this squarely in the document-weaponization threat category common to PDF toolchains. Adobe PSIRT has issued advisory APSB26-141; no public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write (CWE-787) in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution in the context of the current user when a victim opens a crafted malicious PDF or document file. Affected versions span Acrobat 2024 up to 24.001.30383 and both Acrobat and Acrobat Reader through 26.002.21900, per Adobe PSIRT advisory APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, though the C:H/I:H/A:H CVSS impact and prevalence of Adobe Reader in enterprise environments make this a meaningful patching priority.
Use-after-free (CWE-416) in Adobe Acrobat Reader enables arbitrary code execution at the current user's privilege level when a specially crafted document is opened. All Acrobat Reader builds through 26.002.21900 and Acrobat 2024 through 24.001.30383 are affected, as confirmed by Adobe PSIRT under security bulletin APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, but the file-borne delivery mechanism makes this a classic phishing/email-attack vector in enterprise environments.
Use-after-free memory corruption in Adobe Acrobat Reader and Acrobat (continuous track ≤26.002.21900; 2024 classic track ≤24.001.30383) enables arbitrary code execution in the context of the victim's user account. The flaw is triggered when a victim opens a specially crafted PDF file, making phishing campaigns and malicious web downloads the primary real-world delivery vectors. No active exploitation (CISA KEV) or public proof-of-concept has been identified at time of analysis, but the attack primitive is consistent with historically weaponized Acrobat vulnerabilities.
Use After Free in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution in the context of the current user when a victim opens a maliciously crafted PDF or document file. All versions through 26.002.21900 (continuous track) and 24.001.30383 (Classic 2024) are confirmed affected per EUVD-2026-74104. No public exploit or CISA KEV listing has been identified at time of analysis, but the local-execution, user-interaction requirement limits automated mass exploitation while remaining highly practical in phishing and spear-phishing campaigns.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Remote code execution in Google Chrome's DevTools component before 153.0.8010.36 stems from a use-after-free (CWE-416) that, per the advisory, allows a crafted HTML page to execute arbitrary code outside the browser sandbox. All desktop Chrome builds prior to the fixed stable release are affected; the flaw was reported internally by the Chrome team, is fixed in the stable channel, and has no public exploit identified at time of analysis. Notably, the assigned CVSS is 9.6 (Critical) while Chromium itself rated the security severity only 'Low', a significant conflict discussed below.
Sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox via a crafted HTML page. The flaw resides in the Storage component's incorrect reference resolution (CWE-706), making this a second-stage exploit that chains with a separate renderer compromise to achieve full sandbox breakout. No public exploit has been identified at time of analysis, and the fix is available in the stable channel release 153.0.8010.36.
Sandbox-escaping remote code execution in Google Chrome's WebPackaging component affects all desktop versions prior to 153.0.8010.36. A use-after-free (CWE-416) reachable from a crafted HTML page can let a remote attacker potentially execute arbitrary code outside the renderer sandbox with no authentication, requiring only that the victim visit a malicious page. No public exploit has been identified at time of analysis; Chromium's own internal triage rated the security severity 'Low', which sits in notable tension with the 9.6 CVSS assigned to the record.
Remote code execution in Google Chrome on iOS before 153.0.8010.36 stems from a use-after-free in the Sharing component (CWE-416), letting a remote attacker who lures a victim to crafted network content execute arbitrary code outside the browser sandbox. Google has shipped a patched Chrome build; no public exploit is identified at time of analysis, and Google/Chromium rated the underlying bug 'Medium' severity even though the assigned CVSS base score is 9.6.
Remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the Passwords component that, when triggered via crafted UI interaction and social engineering, can let a remote attacker escape the renderer sandbox and run arbitrary code. All Chrome desktop builds before the 153.0.8010.36 stable release are affected. No public exploit identified at time of analysis, and no EPSS or KEV data was provided; note that Google's Chromium team rated the underlying bug only 'Medium' severity, which sits in tension with the supplied CVSS 9.6.
Sandbox-escaping remote code execution in Google Chrome's Aura windowing layer affects all desktop builds prior to 153.0.8010.36. A remote attacker who lures a victim to a crafted HTML page can trigger a use-after-free (CWE-416) and potentially execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the fix ships in the stable-channel desktop update.
Out-of-bounds write in the Media component of Google Chrome before 153.0.8010.36 allows a remote attacker to potentially execute arbitrary code outside the browser's renderer sandbox by luring a victim to a crafted HTML page. The scope-changing memory-corruption bug carries a CVSS of 9.6 despite Chromium's own 'Medium' severity rating, and a vendor patch is available. There is no public exploit identified at time of analysis.
Remote code execution in Google Chrome on Windows prior to 153.0.8010.36 arises from a type-confusion bug in the browser's Rust code, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Google shipped a fixed build via the Stable channel, and the flaw was reported internally by the Chrome team. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though sandbox-escape memory-corruption bugs in Chrome are historically high-value exploitation targets.
Sandbox-escape remote code execution affects Google Chrome on macOS prior to 153.0.8010.36, where an improper quantity-validation flaw (CWE-1284) in Tint, the WebGPU/WGSL shader compiler in Chromium's Dawn graphics stack, lets a crafted HTML page break out of the renderer sandbox. A remote attacker who lures a victim to a malicious web page can potentially execute arbitrary code with the privileges of the browser process on the host. Google reports a fix is shipped; there is no public exploit identified at time of analysis, and Chromium internally rated the issue Medium severity despite the high provided CVSS.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from a numeric truncation error in the Media component, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The vendor patch is available via the September 2026 stable-channel update; no public exploit is identified at time of analysis. Note a signal conflict: Chromium rated this 'Medium' severity while the supplied CVSS base score is 9.6 Critical.
Remote code execution in Google Chrome for macOS prior to 153.0.8010.36 stems from a use-after-free in the Extensions component, letting a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw carries a CVSS 9.6 (scope-changed, network vector with user interaction), though Chromium's own security team rated it 'Medium'. No public exploit has been identified at time of analysis, and the fix is available in the stable channel.
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. With an EPSS of 0.30% and no confirmed active exploitation, this functions as a second-stage sandbox-escape primitive rather than a standalone remote attack.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Use-after-free in Google Chrome's DevTools component prior to 153.0.8010.36 enables a local attacker to escape the browser sandbox and execute arbitrary code at the host OS level via a crafted local program. Chromium's own severity rating is 'Medium', reflecting the local access prerequisite, while the CVSS 8.1 score captures the high-impact sandbox-escape outcome once exploitation succeeds. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the EPSS score (0.12%, 2nd percentile) confirms low observed exploitation probability.
Sandbox escape via incorrect authorization in the Views component of Google Chrome on Windows (versions prior to 153.0.8010.36) enables arbitrary code execution outside the browser sandbox. Exploitation requires an attacker to first compromise the renderer process and then leverage social engineering to induce user interaction with a crafted HTML page. No public exploit or KEV listing exists at time of analysis; Chromium's own severity rating of Medium contrasts with the CVSS 8.3 score, reflecting the difficult two-stage attack chain.
Sandbox escape via improper initialization (CWE-665) in Google Chrome's Views UI framework on Windows, prior to version 153.0.8010.36, can lead to arbitrary code execution outside the browser sandbox. The attack is chained: an adversary must first compromise the renderer process through a separate vulnerability, then leverage social engineering to trigger the Views initialization flaw, elevating from renderer-level code execution to full host OS access. No public exploit code has been identified and EPSS sits at 0.28% (20th percentile), consistent with the multi-step prerequisite bar, though the C:H/I:H/A:H impact profile warrants prompt patching.
Sandbox-escaping remote code execution in Google Chrome's Browser process on Windows (all versions prior to 153.0.8010.36) stems from a use-after-free flaw. A remote attacker who lures a victim into opening a crafted HTML page can corrupt reclaimed heap memory in the privileged browser process and execute arbitrary code outside the renderer sandbox. No public exploit identified at time of analysis; the vendor has shipped a fixed stable build.
Uncontrolled search path element in Chrome's Windows CredentialProvider component (CWE-427) enables a local attacker to execute arbitrary code outside the browser sandbox on Windows systems running Chrome prior to 153.0.8010.36. The flaw is a DLL or executable search-order hijacking issue: Chrome's CredentialProvider resolves a dependency by searching an attacker-controllable path, allowing a malicious local program to intercept and execute in place of a legitimate component, with the result escaping Chrome's sandbox entirely. No public exploit code or CISA KEV listing has been identified at time of analysis.
Sandbox-escape remote code execution in Google Chrome for Android before 153.0.8010.36 arises from an integer overflow in the GPU process, letting a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. Fixed in the same 153.0.8010.36 Stable Channel release that addressed several other GPU/media memory-safety bugs; no public exploit identified at time of analysis. Note the rating tension: the input CVSS is 9.6 (Critical) while Google's own Chromium severity is only Medium.
Use-after-free in Chrome's ANGLE graphics layer on Windows enables sandbox escape and arbitrary code execution when a renderer process has already been compromised. Affected versions are all Chrome releases prior to 153.0.8010.36 on Windows; exploitation requires an attacker to first compromise the renderer and then deliver a crafted HTML page triggering the ANGLE memory corruption. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.28% (20th percentile) reflects low observed exploitation probability.
Chrome's Extensions subsystem prior to 153.0.8010.36 fails to correctly enforce security policies when inputs originate from a compromised renderer process (CWE-807), enabling a two-stage sandbox escape that results in arbitrary code execution outside the Chrome sandbox on the host OS. Exploitation chains a prior renderer compromise with social engineering to bypass Extensions-mediated policy decisions. No public exploit code exists and EPSS is low (0.30%, 22nd percentile), consistent with Chromium's internal 'Medium' severity rating despite the CVSS 8.3 score - reflecting the substantial pre-condition barrier.
Heap-based buffer overflow in the WebRTC component of Google Chrome prior to 153.0.8010.36 allows a remote unauthenticated attacker to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. The RCE is sandbox-confined (CVSS S:U), meaning a chained sandbox-escape exploit would be needed for full host-level compromise. No public exploit or active exploitation has been identified at time of analysis, and EPSS sits at a low 0.24% (15th percentile), consistent with Chromium's own 'Medium' severity designation despite the 8.8 CVSS base score.
Sandbox-escape remote code execution in Google Chrome's Extensions component (versions prior to 153.0.8010.36) lets a remote attacker potentially run arbitrary code outside the renderer sandbox by delivering crafted network traffic. The root cause is incorrect reference resolution (CWE-706), where a name or reference is resolved to the wrong target. Google has shipped a fix; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.20%).
Sandbox escape via confused deputy in Chrome's DataTransfer component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox by directing the victim to a crafted HTML page. Fixed in Chrome 153.0.8010.36, this is classified 'Medium' severity by the Chromium team despite the CVSS 8.3 score with full scope change (S:C, C:H/I:H/A:H), reflecting that renderer pre-compromise is required. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS is 0.25% (16th percentile).
Sandbox escape in Google Chrome's Extensions component (versions prior to 153.0.8010.36) permits an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via crafted network traffic. The missing authorization check (CWE-862) in the Extensions subsystem fails to enforce inter-process privilege boundaries, converting a renderer-level foothold into host-level code execution. No public exploit or active exploitation has been identified; EPSS sits at 0.19%, though SSVC rates the technical impact as 'total' given successful exploitation fully bypasses Chrome's sandbox isolation.
Sandbox escape via incorrect authorization in the WebView component of Google Chrome on Android (prior to 153.0.8010.36) allows a network-based attacker to execute arbitrary code outside the Chrome renderer sandbox. Exploitation is a two-stage process: the attacker must first compromise the renderer process, then leverage the CWE-863 authorization flaw in WebView to break out of the sandbox via a crafted HTML page. No public exploit or KEV listing has been identified at time of analysis; EPSS is low at 0.30%, consistent with the complexity barrier of requiring a prior renderer compromise.
Sandbox-escape via race condition in Google Chrome's Updater component on Windows allows a local, unprivileged attacker to execute arbitrary code outside the Chrome sandbox. Affected versions are all Chrome releases for Windows prior to 153.0.8010.36, fixed in the September 2026 stable channel update. No public exploit has been identified and EPSS sits at 0.10% (1st percentile), but successful exploitation yields full C:H/I:H/A:H impact beyond the sandbox boundary. Chromium's own rating of 'Medium' reflects the high attack complexity imposed by the race condition timing requirement.
Privilege elevation in Chrome's WebUI component prior to version 153.0.8010.36 enables sandbox escape and arbitrary code execution outside the browser sandbox when the renderer process has already been compromised. This is a second-stage, chained exploit: an attacker must first achieve renderer-level code execution (e.g., via a separate renderer bug) and then leverage this WebUI flaw (CWE-250 - execution with unnecessary privileges) to break out of the sandbox. No public exploit code has been identified and no CISA KEV listing exists; SSVC rates automatable exploitation as 'no', consistent with the multi-step chain requirement.
Sandbox-escape remote code execution in Google Chrome before 153.0.8010.36 stems from incorrect reference resolution in the FileSystem component, letting a remote attacker who lures a victim into visiting a crafted HTML page run arbitrary code outside the renderer sandbox. Reported by Google's own Chrome team and patched in the 2026-09 stable-channel desktop update; no public exploit is identified and SSVC lists exploitation as none, with EPSS at a modest 0.32%. Note a signal conflict: Chromium rates this 'Medium' while the assigned CVSS is 9.6, and the description requires user interaction (social engineering), so real-world risk is lower than the raw score suggests.
Sandbox escape via improper input validation in Chrome's SiteIsolation component allows an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox. Affected versions are all Chrome releases prior to 153.0.8010.36. Exploitation requires chaining this flaw with a separate renderer compromise - an attacker must first gain control of the renderer (typically via another renderer-targeted vulnerability), then use this SiteIsolation validation flaw to break out of the sandbox and execute code in a more privileged process context. No public exploit code or active exploitation has been identified at time of analysis.
Type confusion (CWE-843) in Chrome's XML processing component allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by enticing a target to visit a crafted HTML page. All Chrome desktop versions prior to 153.0.8010.36 are affected across Windows, macOS, and Linux. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the impact is further bounded by Chrome's sandbox architecture, which prevents direct OS-level code execution without a secondary sandbox-escape primitive.
Use-after-free in Chrome's Chromecast component allows remote attackers to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Affected are all Google Chrome releases prior to 153.0.8010.36 across desktop platforms. Exploitation is sandboxed - code execution is confined to the renderer process - but the C:H/I:H/A:H impact rating reflects full compromise of data accessible within that context. No active exploitation has been confirmed and no public proof-of-concept code is known at time of analysis.
Sandbox escape in Google Chrome's FileSystem component prior to 153.0.8010.36 stems from missing authorization checks (CWE-862), allowing arbitrary code execution outside the renderer sandbox. The attack is multi-stage: an attacker must first compromise the renderer process via a separate exploit, then serve a crafted HTML page using social engineering to trigger the authorization gap and escape the sandbox. No active exploitation is confirmed (not in CISA KEV; EPSS 0.34% at 27th percentile; SSVC exploitation: none), and the renderer pre-compromise requirement substantially limits real-world attack surface.
Out-of-bounds write in Chrome's V8 JavaScript engine allows remote attackers to execute arbitrary code within the renderer sandbox by directing a user to a crafted HTML page. All Google Chrome versions prior to 153.0.8010.36 are affected across desktop platforms. Impact is bounded by Chrome's renderer sandbox - an attacker achieves control over the renderer process and can access browser-stored data such as session cookies and saved credentials, but reaching the host OS would require a separately chained sandbox escape exploit. No public exploit identified at time of analysis.
Sandbox-escaping remote code execution in Google Chrome (desktop) prior to 153.0.8010.36 stems from a use-after-free in the browser's Core component that a remote attacker can trigger through a maliciously crafted Chrome extension. Successful exploitation lets attacker-controlled code run outside the renderer sandbox with the browser process's privileges, but it requires convincing the victim to install or interact with the malicious extension (social engineering). There is no public exploit identified at time of analysis, EPSS is low (0.24%, 15th percentile), and CISA SSVC records exploitation as none, so the risk is high-impact but currently unproven in the wild.
Remote code execution in Google Chrome before 153.0.8010.36 stems from a use-after-free in the browser's Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the renderer sandbox. Chromium rates the severity High, and the supplied CVSS is 9.6 reflecting the sandbox-escape scope change. EPSS is low (0.35%, 29th percentile) and no public exploit is identified at time of analysis.
Remote code execution inside the Chrome sandbox is possible in Google Chrome versions prior to 153.0.8010.36 via a use-after-free vulnerability in the V8 JavaScript engine, triggered by a specially crafted HTML page. An unauthenticated remote attacker who can lure a user to a malicious page can execute arbitrary code within the Chrome renderer process sandbox - a significant foothold even without a sandbox escape. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.21% reflects low observed exploitation activity, though V8 UAF primitives are historically attractive to threat actors.
Type confusion in V8 (CWE-843) in Google Chrome prior to 153.0.8010.36 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by delivering a crafted HTML page. All desktop Chrome installations on unpatched versions are affected, exploitable via drive-by browsing without any authentication or special privileges beyond convincing the victim to visit a malicious page. No public exploit or CISA KEV listing has been confirmed at time of analysis; SSVC rates technical impact as total but exploitation as none, consistent with a low EPSS of 0.23%.
Sandbox-escape code execution in Google Chrome's Printing subsystem (all versions prior to 153.0.8010.36) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a crafted HTML page, leveraging a use-after-free in the print handling path. This is a secondary exploit in a multi-stage chain: renderer compromise is a hard prerequisite, not something this bug alone provides. No public exploit code has been identified and CISA KEV does not list this vulnerability as actively exploited.
Sandbox-escaping remote code execution in Google Chrome's Payments component (versions prior to 153.0.8010.36) lets a remote attacker who successfully social-engineers a victim into visiting a crafted HTML page trigger a use-after-free and potentially run arbitrary code outside the renderer sandbox. Chromium rates the security severity 'High'; the supplied CVSS is 9.6 reflecting scope change and full CIA impact. No public exploit is identified at time of analysis and EPSS is low (0.26%, 17th percentile), and CISA SSVC records exploitation status as none.
Remote code execution in Google Chrome on macOS prior to 153.0.8010.36 stems from a use-after-free in the Payments component, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the browser sandbox. The provided CVSS vector (9.6) reflects a scope-changing sandbox escape requiring user interaction (a page visit), while Chromium rated the underlying bug 'High' rather than 'Critical'. A vendor patch is available; EPSS is low (0.30%, 22th percentile) and no public exploit is identified.
Sandbox-escape remote code execution in Google Chrome's Device component on macOS (versions prior to 153.0.8010.36) allows a remote attacker to potentially run arbitrary code outside the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) reported by Google's own Chrome team; Chromium assigned it 'High' severity while the CVSS base score is 9.6. No public exploit identified at time of analysis, and EPSS is low (0.26%).
Use-after-free in V8, Chrome's JavaScript engine, enables remote code execution within the browser's renderer sandbox when a victim visits a crafted HTML page. All Chrome releases prior to 153.0.8010.36 are affected across desktop platforms. No public exploit has been identified and EPSS sits at 0.21% (12th percentile), but SSVC rates the technical impact as total, and the Chromium security team classified this as High severity.
Use-after-free in Chrome's WebPackaging component enables full sandbox escape to arbitrary code execution for attackers who have already established a foothold in the renderer process. All Chrome desktop releases prior to 153.0.8010.36 are affected. No public exploit code has been identified and EPSS is low (0.34%), but the scope-changed CVSS vector (S:C, C:H/I:H/A:H) confirms that successful exploitation fully escapes Chrome's multi-process sandbox, translating a renderer compromise into OS-level code execution.
Use-after-free in Chrome's Input component enables in-sandbox remote code execution against all Chrome versions prior to 153.0.8010.36. The vulnerability is triggered when a victim visits a crafted HTML page, requiring no authentication and no special configuration - only a single browse action. Google has rated this High severity, the patch is available in 153.0.8010.36, and no public exploit has been identified at time of analysis, with EPSS at 0.21%.
Use-after-free in Chrome's Platform component (all versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a crafted HTML page. The Chromium team rated this 'High' severity - consistent with the CVSS 8.8 score and distinguishing it from Critical-rated full sandbox-escape vulnerabilities addressed in the same release cycle. No public exploit code has been identified, and the EPSS score of 0.21% (12th percentile) reflects limited observed exploitation activity at this time; no CISA KEV listing exists.
DevTools injection (CWE-74) in Google Chrome prior to 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to escape the Chromium sandbox and execute arbitrary code on the host system via a crafted HTML page. Chromium rated this 'High' severity; the CVSS 3.1 score of 8.3 (AC:H/S:C) accurately reflects the elevated complexity imposed by the prerequisite renderer compromise and the full scope-change impact. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.25% (16th percentile) confirms low current exploitation probability.
Sandbox-escaping remote code execution in Google Chrome before 153.0.8010.36 stems from improper array-index validation (CWE-129) in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can potentially corrupt memory and execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; no public exploit is identified at time of analysis and EPSS is low (0.21%).
Remote code execution outside the browser sandbox affects Google Chrome versions prior to 153.0.8010.36 through a use-after-free flaw in the Web Authentication (WebAuthn) component. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code with the privileges of the browser process, escaping the renderer sandbox (scope change). No public exploit has been identified at time of analysis and EPSS is low (0.34%), but the sandbox-escape RCE nature and Chrome's enormous install base make prompt patching important.
Remote code execution in Google Chrome's ANGLE graphics component on Windows (versions prior to 153.0.8010.36) allows a remote attacker to trigger an out-of-bounds write and potentially execute arbitrary code outside the browser sandbox via a crafted HTML page. Rated Chromium 'High' with a CVSS of 9.6 reflecting a scope-changing sandbox escape, though exploitation requires the victim to load malicious web content. No public exploit identified at time of analysis, and EPSS is low (0.21%), consistent with CISA SSVC scoring exploitation as 'none'.
Out-of-bounds read in ANGLE, Chrome's cross-platform graphics abstraction layer, enables sandbox escape and potential remote code execution on the host system for Chrome versions prior to 153.0.8010.36. This is a staged, second-phase exploit: an attacker must first compromise the renderer process through a separate vulnerability before leveraging this ANGLE flaw to break out of Chrome's sandbox via a crafted HTML page. No public exploit has been identified and no CISA KEV listing exists; EPSS at 0.21% (12th percentile) reflects minimal observed exploitation activity at time of analysis.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a heap buffer overflow in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can corrupt heap memory and execute arbitrary code outside the renderer sandbox, gaining full compromise of the host. No public exploit is identified at time of analysis and EPSS is low (0.33%), but the sandbox-escape scope and Chrome's near-universal footprint make prompt patching essential.
Out-of-bounds read in the WebGL component of Google Chrome before 153.0.8010.36 lets a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the browser sandbox. Chromium rates the security severity as High, and a vendor patch is available; no public exploit has been identified and CISA SSVC records exploitation as none, with EPSS at a low 0.28% (20th percentile).
Use-after-free in Chrome's Views UI framework enables local attackers to escape the browser sandbox and execute arbitrary code at browser-process privilege level. The vulnerability affects all Google Chrome desktop versions prior to 153.0.8010.36. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects low near-term exploitation probability.
Sandbox-escape remote code execution in Google Chrome on Android (versions prior to 153.0.8010.36) stems from a use-after-free in Dawn, Chromium's WebGPU implementation. A remote attacker who lures a victim to a crafted HTML page can trigger the freed-object reuse to execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; there is no public exploit or CISA KEV listing, and EPSS is low (0.30%), indicating no evidence of active or widespread exploitation at time of analysis.
Sandbox-escape remote code execution in Google Chrome (Chromium-based desktop) before 153.0.8010.36 stems from an incorrect authorization flaw in the DevTools component. A remote attacker who lures a victim to a crafted HTML page can potentially execute arbitrary code outside the renderer sandbox, achieving full compromise of the browser process. No public exploit identified at time of analysis; EPSS is low (0.21%, 11th percentile) and the issue is not in CISA KEV, but Google rates the Chromium security severity as High.
Sandbox-escape code execution via a race condition in the Google Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox. Affected builds are all Chrome versions prior to 153.0.8010.36 on Windows. The Chrome Updater's elevated-privilege execution context makes winning the race condition particularly impactful, as successful exploitation bypasses sandbox containment entirely.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local unprivileged attacker to execute arbitrary code outside the Chrome renderer sandbox by exploiting a race condition. All Chrome for Windows releases prior to 153.0.8010.36 are affected. No public exploit has been identified at time of analysis; EPSS places exploitation probability at the 3rd percentile, though SSVC rates technical impact as 'total,' reflecting full system compromise potential if the race condition is successfully won.
Use-after-free in Google Chrome's Core component on Windows prior to 153.0.8010.36 enables a renderer-compromised attacker to escape the browser sandbox and execute arbitrary code on the host OS. The vulnerability is platform-specific to Windows and functions as the second stage of a chained exploit: an attacker must first achieve renderer-level compromise before triggering this UAF to pivot into the privileged browser process. No public exploit code or active exploitation has been identified at time of analysis; vendor patch 153.0.8010.36 is available.
Use-after-free in Chrome's Receiver component allows an adjacent, unauthenticated attacker to execute arbitrary code outside the renderer sandbox via crafted network traffic, affecting all Chrome versions prior to 153.0.8010.36. The scope change in the CVSS vector confirms this is a full sandbox escape - successful exploitation yields OS-level code execution on the victim machine without requiring any user interaction. No public exploit has been identified at time of analysis, and EPSS at 0.13% (3rd percentile) indicates low observed exploitation activity.
Sandbox-escape remote code execution in Google Chrome's Views UI framework prior to 153.0.8010.36 allows a local attacker to execute arbitrary code outside the browser sandbox by inducing a specific UI interaction that triggers a use-after-free condition. The CVSS scope change (S:C) confirms the vulnerability crosses the renderer sandbox boundary into the broader OS context, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified at time of analysis; EPSS of 0.20% (10th percentile) reflects low automated exploitation probability, though sandbox escapes are high-value for privilege escalation chains.
Out-of-bounds read in Google Chrome's Media component (versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a specially crafted HTML page. The vulnerability stems from improper bounds checking during media processing, allowing a remote attacker to read memory beyond intended buffer limits and leverage the resulting data to achieve arbitrary code execution. No public exploit has been identified at time of analysis and EPSS is low (0.35%), but the attack surface is broad given Chrome's ubiquity.
Memory corruption in the Codecs component of Google Chrome prior to 153.0.8010.36 enables remote unauthenticated attackers to execute arbitrary code inside the browser sandbox by delivering a crafted HTML page containing malformed media content. The flaw is classified CWE-119 (improper bounds restriction), rated 'High' by Chromium Security, and carries a CVSS 8.8 base score with a network attack vector requiring only passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS stands at a low 0.35% (29th percentile), indicating theoretical rather than observed exploitation.
Double-free memory corruption in PDFium (Chrome's PDF rendering engine) on Windows allows remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF file. Affected versions are all Chrome releases on Windows prior to 153.0.8010.36, where CWE-415 double-free in the PDFium component enables an attacker-controlled allocation state. No public exploit or CISA KEV listing is confirmed at time of analysis, and EPSS remains low at 0.20% (10th percentile), suggesting exploitation is not yet widespread despite the network-reachable vector.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a use-after-free in ANGLE, Chrome's graphics abstraction layer that translates OpenGL ES calls to Direct3D. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code outside the browser sandbox, giving full compromise of the renderer host process. No public exploit identified at time of analysis, and EPSS is modest (0.35%), but the sandbox-escape impact and one-click delivery make this a high-priority browser patch.
Use-after-free in Chrome's Cast (Chromecast streaming) component allows an adjacent unauthenticated attacker to potentially escape the browser sandbox and execute arbitrary code by delivering crafted network traffic over a local or Wi-Fi network. All Chrome desktop versions prior to 153.0.8010.36 are affected, with Chromium rating this Critical due to the full-CIA, scope-changed impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.17% (6th percentile) indicates minimal observed exploitation activity despite the high severity classification.
Remote code execution in Google Chrome prior to 153.0.8010.36 allows a remote attacker to escape the renderer sandbox and run arbitrary code on the host by luring a victim to a crafted HTML page that triggers a heap buffer overflow in the WebGL implementation. Chromium rates this Critical and the CVSS 9.6 score reflects a scope-changing sandbox escape; no public exploit is identified at time of analysis, and EPSS is low at 0.29% (21st percentile). Patched in the September 2026 stable-channel desktop release.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 arises from an out-of-bounds write in the WebGL graphics subsystem, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the renderer sandbox. Rated Critical by Chromium and CVSS 9.6, the scope-changed vector reflects a full sandbox escape. No public exploit is identified at time of analysis and EPSS is low (0.39%), but WebGL memory-corruption bugs are historically high-value targets.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 stems from a use-after-free in the WebGL implementation that a remote attacker can trigger with a crafted HTML page to execute arbitrary code outside the browser sandbox. Chromium rates this Critical and the CVSS is 9.6, reflecting a full renderer-to-sandbox-escape chain requiring only that a victim visit a malicious page. No public exploit is identified at time of analysis and EPSS is low (0.36%), but the sandbox-escape impact makes it a priority patch.
Remote code execution in Google Chrome desktop prior to 153.0.8010.36 arises from a use-after-free in the WebGL implementation, allowing a remote attacker to run arbitrary code outside the browser sandbox by luring a victim to a crafted HTML page. Google rates the Chromium severity as Critical and the CVSS is 9.6, reflecting a full renderer-to-host sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.28% (20th percentile).
Arbitrary code execution in Actions Semiconductor's Tool - Media Player Utilities v4.46 lets a physically proximate attacker run code on a host by abusing the Production.dll and RdiskUpgrade.exe firmware/disk-upgrade components (CWE-94 code injection). The flaw affects this specific flashing/production utility bundled with Actions Semiconductor media-player SoC toolchains. SSVC rates technical impact as total with a public proof-of-concept, but EPSS is only 0.17% (6th percentile), and the required physical/local proximity sharply limits real-world reach.
Code injection in n8n's legacy expression engine allows an authenticated user to replace the mutable global JSON.stringify function within expression evaluation, causing subsequent code-generation paths to embed and execute attacker-controlled JavaScript. Affected are all n8n versions prior to 1.123.76 (v1 branch), 2.37.7, and 2.38.2. The vulnerability is confined to the legacy expression engine (isolated-vm-bridge.ts and ExpressionBuilder.ts); the vm expression engine is unaffected. No public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in n8n workflow automation platform prior to versions 1.123.76, 2.37.7, and 2.38.2 is achievable by any authenticated user who can author workflow expressions. The root cause is a sandbox escape in the PrototypeSanitizer AST hook: because the sanitizer references itself via dynamically scoped `this`, a crafted class field named `__sanitize` rebinds the sanitizer function, after which the expression freely invokes the JavaScript `Function()` constructor and executes arbitrary Node.js code on the backend. No public exploit has been identified at time of analysis, but the Function constructor escape technique is well-documented in the JavaScript security research community, lowering the barrier to independent rediscovery.
Remote code execution in Apache Impala 2.7.0 through 4.5.1 allows an authorized user with table-creation and remote-storage upload privileges to load and execute arbitrary Java classes on Impala daemon nodes by exploiting insufficient authorization controls over External Data Source tables. The vulnerability abuses Impala's legitimate extensibility feature - Data Source tables - which permits custom Java class loading from remote storage; insufficient authorization checks mean any user holding those two combined privileges can weaponize the feature for server-side code execution. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; upgrade to 4.5.2 is the vendor-confirmed fix.
Local privilege escalation in Auth0 AD/LDAP Connector versions up to and including 6.5.0 allows a low-privileged local user to modify the connector's configuration file due to improper permission handling during service startup processing. When the connector service restarts - whether scheduled, OS-triggered, or manually - the tampered configuration value is evaluated, resulting in code execution with the privileges of the service account running the connector. No public exploit code has been identified at time of analysis, but the straightforward local exploitation path (AC:L) and high impact to a service that often holds privileged Active Directory credentials make this a meaningful risk in environments running on-premise Auth0 connector deployments.
Heap-based buffer overflow in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution at current-user privilege level when a victim opens a crafted PDF or supported file format. Affected versions span Acrobat Reader ≤26.002.21900 and Acrobat 2024 ≤24.001.30383 across all supported platforms, as documented in Adobe advisory APSB26-141. No public exploit code or active exploitation in the wild has been identified at the time of this analysis, but Adobe Acrobat's ubiquity in enterprise document workflows makes this a credible phishing or spear-phishing vehicle.
Use-After-Free in Adobe Acrobat Reader and Adobe Acrobat allows arbitrary code execution in the security context of the current user upon opening a specially crafted PDF file. Affected versions span Acrobat Reader up to 26.002.21900 and Acrobat 2024 up to 24.001.30383, as documented in Adobe advisory APSB26-141. No public exploit identified at time of analysis, but the file-delivery attack vector makes this a realistic phishing and drive-by-download threat given Acrobat Reader's ubiquity as an enterprise PDF handler.
Use After Free in Adobe Acrobat Reader and Acrobat 2024 allows arbitrary code execution in the context of the current user when a victim opens a crafted malicious document. Affected across both the continuous track (≤26.002.21900) and the classic 2024 track (≤24.001.30383), this is a memory corruption vulnerability rooted in improper object lifecycle management within Acrobat's rendering engine. No public exploit code or CISA KEV listing has been identified at time of analysis, but the file-open attack surface and high impact make this a credible phishing or watering-hole delivery risk.
Use-after-free (UAF) in Adobe Acrobat Reader allows arbitrary code execution in the context of the authenticated local user when a victim opens a specially crafted malicious PDF or document file. Affected versions span Acrobat 2024 (≤24.001.30383) and both Acrobat and Acrobat Reader (≤26.002.21900), making the exposure broad across the current release track. No public exploit or active exploitation has been confirmed at time of analysis, but the file-based delivery vector makes this class of vulnerability routinely weaponized via phishing campaigns.
Integer overflow in Adobe Acrobat Reader and Acrobat (all editions through 26.002.21900) and Acrobat 2024 (through 24.001.30383) enables arbitrary code execution within the context of the victim's user account. The flaw is triggered when a user opens a specially crafted PDF file, making social engineering the primary delivery mechanism. No public exploit code or active exploitation has been identified at time of analysis, but the high CIA impact and wide deployment footprint make patching a priority.
Use-after-free (CWE-416) in Adobe Acrobat Reader enables arbitrary code execution in the context of the logged-in user when a victim opens a specially crafted PDF file. Affected versions include Acrobat Reader and Adobe Acrobat up to 26.002.21900 and Acrobat 2024 up to 24.001.30383, as documented in Adobe advisory APSB26-141. No public exploit code or active exploitation has been identified at time of analysis, but the ubiquity of Acrobat Reader across enterprise environments and the reliable code-execution impact make patching a high priority.
Use After Free in Adobe Acrobat Reader allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious document. Affected versions span both the continuous-track Acrobat/Acrobat Reader (≤26.002.21900) and the Acrobat 2024 classic track (≤24.001.30383). No public exploit or CISA KEV listing is identified at time of analysis, but the combination of a widely deployed document reader, file-open delivery vector, and full C/I/A impact makes this a high-priority patching target for enterprise environments.
Out-of-bounds write in Adobe Acrobat Reader and Acrobat allows arbitrary code execution in the context of the opening user when a victim opens a specially crafted malicious file. All versions of Acrobat Reader and Adobe Acrobat through 26.002.21900, and Acrobat 2024 through 24.001.30383, are affected. No public exploit code or CISA KEV listing has been identified at time of analysis, but the file-based delivery mechanism and full C:H/I:H/A:H impact make this a material risk for organizations with unpatched deployments.
Out-of-bounds write in Adobe Acrobat and Acrobat Reader allows arbitrary code execution in the current user's context when a victim opens a specially crafted file. Affected are Acrobat 2024 versions through 24.001.30383 and Adobe Acrobat/Acrobat Reader through 26.002.21900, per Adobe APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, though the ubiquity of Acrobat as an attack surface and the RCE-grade impact make this a priority patch.
Out-of-bounds write in Adobe Acrobat Reader and Acrobat (Continuous track through 26.002.21900; Classic 2024 track through 24.001.30383) enables arbitrary code execution in the context of the victim user. The CWE-787 memory corruption flaw is triggered when a specially crafted document is opened, placing this squarely in the document-weaponization threat category common to PDF toolchains. Adobe PSIRT has issued advisory APSB26-141; no public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write (CWE-787) in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution in the context of the current user when a victim opens a crafted malicious PDF or document file. Affected versions span Acrobat 2024 up to 24.001.30383 and both Acrobat and Acrobat Reader through 26.002.21900, per Adobe PSIRT advisory APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, though the C:H/I:H/A:H CVSS impact and prevalence of Adobe Reader in enterprise environments make this a meaningful patching priority.
Use-after-free (CWE-416) in Adobe Acrobat Reader enables arbitrary code execution at the current user's privilege level when a specially crafted document is opened. All Acrobat Reader builds through 26.002.21900 and Acrobat 2024 through 24.001.30383 are affected, as confirmed by Adobe PSIRT under security bulletin APSB26-141. No public exploit or CISA KEV listing has been identified at time of analysis, but the file-borne delivery mechanism makes this a classic phishing/email-attack vector in enterprise environments.
Use-after-free memory corruption in Adobe Acrobat Reader and Acrobat (continuous track ≤26.002.21900; 2024 classic track ≤24.001.30383) enables arbitrary code execution in the context of the victim's user account. The flaw is triggered when a victim opens a specially crafted PDF file, making phishing campaigns and malicious web downloads the primary real-world delivery vectors. No active exploitation (CISA KEV) or public proof-of-concept has been identified at time of analysis, but the attack primitive is consistent with historically weaponized Acrobat vulnerabilities.
Use After Free in Adobe Acrobat Reader and Acrobat 2024 enables arbitrary code execution in the context of the current user when a victim opens a maliciously crafted PDF or document file. All versions through 26.002.21900 (continuous track) and 24.001.30383 (Classic 2024) are confirmed affected per EUVD-2026-74104. No public exploit or CISA KEV listing has been identified at time of analysis, but the local-execution, user-interaction requirement limits automated mass exploitation while remaining highly practical in phishing and spear-phishing campaigns.