RCE
Monthly
Integer overflow in the Media component of Google Chrome (all versions prior to 155.0.8059.39) allows a remote, unauthenticated attacker to corrupt memory via a crafted HTML page containing specially formed media content, with the potential to execute arbitrary code outside the browser sandbox. Exploitation is not automatic: the CVSS vector (UI:R) confirms the victim must actively load the attacker-controlled or compromised page, and Google rated this a Chromium severity of 'Low', indicating the sandbox-escape outcome is not reliably achievable and probably depends on specific memory conditions or combining this primitive with others. No public exploit code and no CISA KEV entry were identified at time of analysis; the 9.6 score reflects the scope-change metric (S:C) and high C/I/A impact rather than proven real-world exploitation, so the practical risk is lower than the headline score suggests.
Sandbox escape in Google Chrome before 155.0.8059.39 via a heap-based buffer overflow (CWE-122) in ANGLE, Chrome's graphics translation layer: a remote attacker who has already compromised a sandboxed renderer process can use a crafted HTML page to execute arbitrary code outside the sandbox. It is a second-stage primitive rather than an initial-access bug - the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H (8.3) reflects high attack complexity, a required pre-existing renderer exploit chain, and active user interaction (UI:R), with the scope change S:C capturing the crossing of the sandbox boundary, even though Chromium rates the underlying bug Low severity. No public exploit code was identified at time of analysis and CISA's SSVC data records no observed exploitation, so the headline 8.3 should be weighed against the significant preconditions.
Code execution outside the Chrome sandbox on Windows is possible through CVE-2026-106186, an uncontrolled search path flaw in Chrome's CredentialProvider component affecting Chrome builds prior to 155.0.8059.39. The issue is local-only (CVSS:3.1/AV:L) and requires both a pre-existing local foothold with write access to a directory the component searches and user interaction to load the affected program, yet because the credential provider loads in a more privileged Windows context the scope changes (S:C) and confidentiality, integrity, and availability impacts are all High, yielding a base score of 8.6 with no privileges required (PR:N). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; SSVC rates exploitation as 'none' and automatable as 'no', and Chromium's own internal severity rating is 'Low', which sharply tempers the headline CVSS figure. A vendor patch is available as Chrome 155.0.8059.39.
Arbitrary code execution confined to Chrome's renderer sandbox is possible in Google Chrome versions prior to 155.0.8059.39, where an incorrect comparison in the font rendering pipeline can be triggered by a crafted HTML page. This is an unauthenticated remote attack (AV:N/PR:N) that requires the victim to load attacker-controlled web content (UI:R); the resulting code execution stays inside the renderer sandbox (S:U), and escaping to the host operating system requires a separate, unrelated sandbox-escape vulnerability - which is why Chromium assigned a Low security severity despite the CVSS 8.8 base score. No public exploit code was identified at time of analysis, and a vendor-released patch (155.0.8059.39) is available.
Missing authorization in the Actor component of Google Chrome prior to 155.0.8059.39 allows code to escape the browser sandbox, but only after the attacker has already compromised the renderer process via a separate bug and then gets the victim to load a crafted HTML page. This prerequisite, combined with required user interaction (UI:R) and high attack complexity (AC:H) from the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H vector, means the flaw is only usable as a link in an exploit chain rather than as a standalone initial-access vector; the changed scope (S:C) and high confidentiality, integrity and availability impact reflect the potential for full code execution outside the sandbox. No public exploit code identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status, so risk should be weighed against the conflicting 8.3 score versus the demanding exploitation preconditions. A vendor patch is available in Chrome 155.0.8059.39.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Type confusion in V8, Chrome's default JavaScript and WebAssembly engine, enables a remote attacker to run arbitrary code inside the browser's renderer sandbox in Google Chrome releases below 155.0.8059.39. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms the attack is network-reachable and requires no authentication, though it does require the victim to open attacker-controlled web content, so a phishing, malvertising, or watering-hole lure is a prerequisite. No public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as 'none' and the issue as not automatable, so real-world priority currently sits below what the 8.8 base score alone implies; note that code execution is confined to the renderer sandbox, meaning full host compromise would require chaining a separate sandbox-escape flaw. Google has shipped a vendor patch.
Incorrect authorization in the Google Chrome user-interface layer allows a crafted HTML page to escape the renderer sandbox and execute arbitrary code outside it on all Chrome builds prior to 155.0.8059.39. Exploitation requires the victim to open an attacker-supplied page (UI:R in the assessed vector) and, while no authentication is required (PR:N) and no unusual configuration is needed, the attack is not fully remote - it depends on that user action, which is the main limiting factor. Severity signals are mixed: the assessed CVSS vector scores 9.6 with scope change (S:C) and high confidentiality, integrity and availability impact, yet Google rates the underlying Chromium issue as Medium, and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Arbitrary code execution inside the Chrome renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a race condition (CWE-367) in the V8 JavaScript engine can be won by a crafted HTML page. Exploitation requires only that the victim load the attacker's page in a vulnerable browser (UI:R, PR:N per the CVSS vector), with no credentials or prior privileges needed, but success additionally depends on hitting a time-of-check/time-of-use timing window, which our assessment captures by raising attack complexity to High (CVSS 3.1 base 8.1 under AC:H, versus the 8.8 score supplied with the CVE under AC:L). The critical caveat is scope: the code execution achieved stays within the renderer sandbox and does not by itself compromise the host operating system, so full system impact requires chaining a separate sandbox-escape vulnerability. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none (Automatable: no, Technical Impact: total), and a vendor-released patch exists in Chrome 155.0.8059.39.
An out-of-bounds write in the Media component of Google Chrome before 155.0.8059.39 lets a remote attacker corrupt memory and potentially achieve arbitrary code execution outside the browser sandbox when a victim opens an attacker-crafted HTML page containing malicious media content. The attack is fully remote and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N), but it is gated by user interaction (UI:R) - the victim must visit the malicious or compromised page - and the 'outside the sandbox' outcome implies defeating Chrome's process sandbox, which is materially harder in practice than the 9.6 base score suggests. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fixed build.
Incomplete cleanup in Dawn, Chrome's WebGPU implementation, allows a crafted HTML page to potentially corrupt GPU-process state and achieve code execution outside the browser sandbox in Google Chrome builds prior to 155.0.8059.39. Exploitation requires the victim to render attacker-controlled content that reaches the affected WebGPU/Dawn code path (CVSS UI:R with PR:N - unauthenticated remote attackers, but user interaction required), and the outcome is probabilistic rather than a guaranteed silent drive-by; the published base score is 9.6 while Google rates the issue Medium, and our assessed vector raises attack complexity to AC:H to reflect the difficulty of chaining a cleanup flaw into a reliable sandbox escape. No public exploit code has been identified at time of analysis, and Google has released Chrome 155.0.8059.39 as the fix.
Heap-based buffer overflow in Google Chrome's font-handling code (CWE-122) lets an attacker who has already compromised the renderer process execute arbitrary code outside the sandbox when a victim renders a crafted HTML page containing malicious font data. All Chrome builds prior to 155.0.8059.39 on default configurations are affected; exploitation is unauthenticated (PR:N) but requires user interaction (UI:R) and a pre-existing renderer compromise, so it functions as a sandbox-escape chain component rather than a standalone drive-by, and is rated high complexity (AC:H) despite a CVSS base of 8.3 (S:C). No public exploit code has been identified at time of analysis and CISA's SSVC assessment records no exploitation, but the vendor has shipped a fix in 155.0.8059.39.
Use-after-free in Chrome's font handling on Windows allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page; the flaw affects Google Chrome versions prior to 155.0.8059.39. Exploitation requires user interaction (UI:R) - the victim must load attacker-controlled content - and there are no authentication prerequisites (PR:N), but the resulting code execution is confined to the Chrome sandbox, so host-level compromise would require a second, independent sandbox-escape bug. Consistent with the medium severity rating assigned by the Chromium team, CISA's SSVC assessment records no known exploitation and no automatable exploitation path, and no public exploit code has been identified at time of analysis.
Arbitrary code execution outside Chrome's sandbox on Android affects Google Chrome builds prior to 155.0.8059.39, where a missing authorization check (CWE-862) can be abused by a malicious co-installed Android app. The attack is local - it requires an attacker-controlled app to already be present on the same device plus successful social engineering to get the victim to install it and trigger the action - so a default, lone Chrome installation is not directly exploitable. Google rates this Chromium security severity Medium, the vendor CVSS is 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our assessment substitutes UI:R, no publicly available exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is only 0.12% (2nd percentile).
Sandbox escape and potential arbitrary code execution outside the browser sandbox in Google Chrome via a confused-deputy flaw in the Google Lens feature, affecting all desktop releases prior to 155.0.8059.39. Exploitation is not standalone: a remote attacker must first have compromised the Chrome renderer process (a separate renderer-stage bug), then convince the victim to load a crafted HTML page, after which the Lens component can be induced to perform a privileged operation that crosses the sandbox boundary on the renderer's behalf - consistent with the CVSS:3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H and high attack complexity. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV absent, SSVC exploitation: none), but the maximum technical impact rating means the issue is worth prioritizing within normal patch cycles; vendor-released patch: 155.0.8059.39.
Race condition in the V8 JavaScript engine allows remote code execution inside the browser sandbox in Google Chrome builds prior to 155.0.8059.39. A remote, unauthenticated attacker can trigger the flaw by getting a victim to open attacker-supplied HTML that drives V8 into the timing window (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) - the required user interaction is the only precondition, and code execution is confined to the renderer/V8 sandbox, so host compromise would require a second, separate sandbox-escape bug. Google has shipped a fixed stable-channel build, and no public exploit code or confirmed active exploitation was identified at time of analysis (CISA SSVC records Exploitation: none; no KEV listing or PoC in the available sources).
Sandbox escape in Google Chrome on iOS (versions prior to 155.0.8059.39) allows a local attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a local program. The flaw is an incorrect reference resolution (CWE-706) in the Passwords component, rated Medium by Chromium and carrying a CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code or confirmed active exploitation has been identified at time of analysis; a vendor patch is available.
Sandbox escape in Google Chrome on macOS, affecting releases prior to 155.0.8059.39, allows an attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox when the victim views a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, base 8.3) confirms a network-reachable, scope-changing escape that requires user interaction and carries high confidentiality, integrity and availability impact once triggered, but the AC:H rating and CISA SSVC 'Automatable: no' reflect that it cannot be used standalone - a prior renderer compromise is a hard prerequisite. Per the authoritative assessment this is a chained second-stage exploit limited to macOS; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the Mobile component of Google Chrome on iOS allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim is socially engineered into opening a crafted HTML page, fixed in Chrome 155.0.8059.39. Successful exploitation requires user interaction (CVSS vector PR:N/UI:R with S:C), meaning the attack hinges on phishing or a malicious link rather than a zero-click path, and the scope change reflects the assessed ability to escape the sandbox boundary. No public exploit code has been identified at time of analysis and the issue is not a confirmed actively exploited (CISA KEV) vulnerability, but the 9.6 CVSS score and the RCE tag make prompt patching of older mobile Chrome installations the priority.
A use-after-free memory-safety flaw in Google Chrome's Media component lets a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a user loads a crafted HTML page containing malicious media content. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires the victim to visit or load the attacker-controlled page (UI:R), which is the main practical barrier; no credentials or special privileges are needed. There is no public exploit identified at time of analysis and the CISA SSVC assessment records no exploitation, but the vendor has shipped a fix in 155.0.8059.39, and the EPSS-style risk picture is dominated by Chrome's ubiquity and the high CVSS base score (8.8) rather than by observed attacks.
Incorrect authorization in the Search component of Google Chrome for Android before 155.0.8059.39 can allow a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim is socially engineered into opening a crafted HTML page. The vendor-rated Chromium severity is Medium, yet the assessed CVSS is 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) because the flaw crosses a security boundary (scope changed) with high confidentiality, integrity and availability impact. The risk signals conflict and must be weighed carefully: the impact score is severe, but exploitation requires a click of user interaction, is confined to Android builds (desktop Chrome is unaffected), and no public exploit code or confirmed active exploitation has been identified at the time of analysis. Vendor patches are available.
Use-after-free in Google Chrome's garbage-collection code before 155.0.8059.39 allows an unauthenticated remote attacker to corrupt memory and execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (PR:N, UI:R) and the code execution stays contained in the browser sandbox, so OS-level compromise would require chaining a separate sandbox-escape flaw; no public exploit identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', which tempers the high 8.8 CVSS base score. Vendor-released patch: 155.0.8059.39, distributed through Chrome's stable channel.
Use-after-free in the Streaming component of Google Chrome prior to 155.0.8059.39 allows unauthenticated remote attackers to execute arbitrary code inside the renderer sandbox when a victim is socially engineered into loading a crafted HTML page, consistent with the CVSS vector AV:N/AC:L/PR:N/UI:R. Google rates the issue Medium severity (Chromium) while the CVSS base score is 8.8, reflecting high confidentiality, integrity, and availability impact on the renderer process rather than the host. There is no CISA KEV listing and no public exploit identified at time of analysis, and the SSVC assessment records exploitation as none; the primary containment is Chrome's process sandbox, so full host compromise would require chaining a separate sandbox-escape flaw.
Sandbox escape in Google Chrome's WebAppInstalls component allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox when a victim visits a crafted HTML page and is socially engineered into interacting with the web app installation flow. The flaw is a missing authorization check (CWE-862) affecting Chrome versions prior to 155.0.8059.39; the technical impact is total, but the vendor rates it Medium because exploitation requires a prior renderer compromise, deliberate user interaction (UI:R), and high attack complexity (AC:H) rather than a default-configuration remote hit. No public exploit code and no confirmed active exploitation have been identified at time of analysis (CISA SSVC Exploitation: none, Automatable: no).
Use-after-free in Google Chrome allows unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by convincing a victim to load a crafted HTML page, affecting all versions prior to 155.0.8059.39. The attack requires user interaction (UI:R) but no authentication or special configuration, and while code execution is confined to the sandbox, the CVSS 3.1 score is 8.8. No public exploit or active exploitation has been identified, and a vendor patch is available.
A sandbox escape in Google Chrome before 155.0.8059.39 lets an attacker who has already compromised the browser's renderer process trigger a race condition in Chrome's font handling and execute arbitrary code outside the sandbox, via a crafted HTML page the victim must load (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, score 8.3). The prerequisite is significant: a separate, prior renderer compromise is required, and AC:H reflects the non-deterministic nature of winning the race, so this is a chained post-exploitation primitive rather than a standalone drive-by. Unauthenticated from a network perspective, with UI:R meaning the target must open attacker-controlled content; no CISA KEV entry, no public exploit code identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no, though technical impact is total once the race is won. Vendor-released patch: 155.0.8059.39.
Use-after-free in Google Chrome's Track component before 155.0.8059.39 allows an unauthenticated remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The CVSS 3.1 base score is 8.8 (High) with UI:R, meaning exploitation requires user interaction but no authentication; successful code execution remains confined to Chrome's renderer sandbox and would require a separate sandbox-escape bug to affect the host OS. No public exploit identified at time of analysis, and SSVC records Exploitation: none; CISA KEV does not list this CVE.
Use-after-free in Google Chrome's built-in PDF handling (fixed in 155.0.8059.39) lets remote, unauthenticated attackers execute arbitrary code inside the Chrome renderer sandbox when a victim opens a crafted PDF file - exploitation is not automatic and depends entirely on the user interaction of opening the document (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-416). Because the code execution is confined to the sandboxed renderer, turning this into full host compromise would require chaining a separate sandbox-escape bug; the advisory rates it Chromium severity High. At the time of analysis there is no public exploit identified and CISA SSVC records exploitation as none, though the vulnerability is fully described and a vendor patch plus the underlying Chromium issue tracker entry are publicly referenced. Google Chrome versions before 155.0.8059.39 are affected on all platforms tracked under cpe:2.3:a:google:chrome.
Google Chrome builds prior to 155.0.8059.39 contain a use-after-free in PDF handling that allows a remote, unauthenticated attacker to execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page that embeds a malicious PDF. Exploitation requires the user to open attacker-controlled web content processed by Chrome's built-in PDF (PDFium) viewer - a mandatory interaction step (CVSS UI:R) with no zero-click vector, and any code execution is confined to the sandboxed renderer unless chained with a separate sandbox escape. There is no public exploit identified at time of analysis, SSVC records no observed exploitation and rates the issue not automatable, but technical impact is rated total given high confidentiality, integrity, and availability impact; a vendor patch exists in 155.0.8059.39.
Use-after-free in Google Chrome's V8 JavaScript engine (all releases prior to 155.0.8059.39) lets unauthenticated remote attackers execute arbitrary code inside the renderer sandbox when a victim navigates to an attacker-controlled page containing crafted HTML/JavaScript. The bug carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium's own 'High' severity rating, and because the V8 engine is enabled by default in every standard installation, no special configuration or privileges are needed on the target side. Impact is bounded, however: per the vendor description code execution is confined to the sandbox, so a standalone exploit does not by itself compromise the host and a separate sandbox-escape would be required, and no public exploit identified at time of analysis (SSVC Exploitation: none, Automatable: no) - a genuine priority-worthy issue whose urgency is tempered by the required user interaction, sandbox confinement, and absence of observed exploitation.
Use-after-free in the Media component of Google Chrome prior to 155.0.8059.39 lets a remote attacker execute arbitrary code within the browser's renderer sandbox by luring a victim to open a crafted HTML page. The flaw carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or prior privileges are required, but successful exploitation depends on the user actively navigating to attacker-controlled content. There is no public exploit identified at time of analysis - CISA's SSVC assessment lists exploitation as 'none' - and code execution is contained within the renderer sandbox, so a separate sandbox-escape would be needed to reach the host OS; the vendor has released a patched build.
Type confusion in the V8 JavaScript engine of Google Chrome prior to 155.0.8059.39 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page; the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, so the sole prerequisite is that the victim renders attacker-controlled content in an unpatched desktop build. No public exploit code or active exploitation was identified at time of analysis, and CISA KEV does not list this CVE. The vendor-released patch is Chrome 155.0.8059.39, and installations already updated past that version are not affected. Because the impact is scoped to the sandbox (S:U) per the description, full host compromise would require chaining a separate sandbox-escape vulnerability.
Google Chrome versions prior to 155.0.8059.39 contain a use-after-free in the WebRTC component that a remote, unauthenticated attacker can trigger by convincing a victim to visit a crafted HTML page, resulting in arbitrary code execution within the renderer sandbox (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not automatable and requires user interaction, and the resulting code execution is confined to Chrome's renderer sandbox per the vendor description, so full host compromise would additionally require chaining a separate sandbox-escape flaw. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records no known exploitation; Chrome's built-in auto-update is the primary exposure-reduction control, as patched versions 155.0.8059.39 and later are not vulnerable.
Arbitrary code execution inside the renderer sandbox is achievable in Google Chrome builds prior to 155.0.8059.39, where a use-after-free in the browser's Media component can be triggered when a victim loads a crafted HTML page. Scoring 8.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, the bug requires no authentication but does require the user to visit attacker-controlled content, and because the resulting code execution is confined to the renderer sandbox, full host compromise would require chaining a separate sandbox-escape flaw. A vendor patch is available in the Chrome Stable channel update, and no public exploit has been identified at time of analysis - this is a high-priority patching item rather than an emergency.
Arbitrary code execution confined to the renderer sandbox in Google Chrome builds prior to 155.0.8059.39, reachable when a user opens a crafted HTML page that drives the DevTools state-validation path into an inconsistent state. The flaw is network-delivered and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N), but exploitation is gated by mandatory user interaction (UI:R), which is why CISA's SSVC decision framework rates it as not automatable. No public exploit code and no confirmed active exploitation were identified at time of analysis; Google rates the Chromium severity as High and has shipped a fixed build, so the practical exposure is limited to unpatched clients that have not yet received the auto-update.
Use-after-free in Google Chrome's Media component allows a remote attacker to execute arbitrary code inside the browser's renderer sandbox by luring a victim into loading a crafted HTML page in any Chrome build prior to 155.0.8059.39. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), consistent with Google's own 'High' Chromium security severity, and requires no authentication or privileges on the victim host beyond the user visiting the malicious content (UI:R). Exploitation is confirmed to be constrained by user interaction and by the renderer sandbox - CISA SSVC scores it Exploitation: none, Automatable: no, Technical Impact: total - and there is no public exploit identified at time of analysis, though a vendor-released patch is available.
Use-after-free in Google Chrome's parser allows remote, unauthenticated attackers to execute arbitrary code inside the renderer sandbox by convincing a victim to load a crafted HTML page, affecting all Chrome versions prior to 155.0.8059.39. Exploitation requires user interaction (the victim must visit or open the malicious page), and the resulting code execution is contained by Chrome's renderer sandbox, so full host compromise would require chaining with a separate sandbox-escape vulnerability. A vendor patch is available in 155.0.8059.39, and no public exploit identified at time of analysis, with CISA's SSVC assessment recording exploitation as none.
Remote code execution inside the renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a use-after-free in the Media component can be triggered by a crafted HTML page. Exploitation requires the victim to load attacker-controlled web content (UI:R) but no authentication or special privileges (PR:N), so default desktop installs are affected; resulting code execution is contained within the renderer sandbox rather than the host operating system. At time of analysis there is no public exploit identified at time of analysis per available intelligence (SSVC exploitation: none, automatable: no), and a vendor patch is available from Google. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium security severity High, this is a genuine high-priority patching item, though the signals are mixed on urgency.
A use-after-free in Chrome's Metrics component (CWE-416) lets an attacker who has already compromised a sandboxed renderer process execute arbitrary code outside the sandbox - a sandbox-escape primitive rather than an initial-access bug. Only users running Chrome versions below 155.0.8059.39 are affected; the flaw is unauthenticated from the network perspective (PR:N) but requires the victim to load attacker-controlled crafted HTML (UI:R) and carries High attack complexity (AC:H) because the attacker must win a use-after-free race and defeat sandbox mitigations. Google has released a fix in Chrome 155.0.8059.39, no public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none, and the overall posture is patch-promptly-but-not-emergency rather than urgent.
Use-after-free in Google Chrome's Select component before version 155.0.8059.39 allows unauthenticated remote attackers to execute arbitrary code inside the browser's renderer sandbox, but only after socially engineering a victim into opening a crafted HTML page (CVSS 3.1 8.8, AV:N/AC:L/PR:N/UI:R). The impact is confined to the sandbox, so compromise of the host operating system would require chaining a separate sandbox-escape vulnerability. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google - the reporting party - has released a fixed build.
Remote code execution inside the Chrome renderer sandbox is possible on Chrome builds prior to 155.0.8059.39, where a use-after-free in the WebRTC component can be triggered by a crafted HTML page. The flaw is rated 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and assigned Chromium severity High; no authentication or prior privileges are required, but the victim must open or be redirected to the attacker's page (UI:R). Impact is confined to the renderer sandbox - reaching the host OS would require chaining a separate sandbox-escape vulnerability - and no public exploit was identified at time of analysis; the primary exposure window is the short period before Chrome's auto-update moves users to the fixed build.
Remote code execution inside the Chrome renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a use-after-free defect in the HTML handling path can be triggered by a crafted HTML page. Any user running an unpatched desktop Chrome who loads attacker-controlled web content (CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) can be targeted; no credentials or elevated privileges are required, but mandatory user interaction (UI:R) and the renderer sandbox confinement limit the direct blast radius, since escaping the sandbox to the host OS would require a separate, distinct vulnerability not covered by this CVE. Google has shipped a vendor patch (155.0.8059.39) and the issue was reported through the Chrome vulnerability program with a Chromium severity rating of High; no public exploit code and no confirmed active exploitation have been identified, and the affected-code flaw is consistent across the CPE wildcard for google:chrome.
Use-after-free in Google Chrome's Web Audio implementation affects versions prior to 155.0.8059.39, where a remote attacker can achieve arbitrary code execution inside the browser's renderer sandbox by getting a victim to open a crafted HTML page that exercises the Web Audio API. The flaw carries an assessed CVSS of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or non-default configuration is required, but the attack does depend on user interaction (loading the page) and the resulting code execution is confined to the renderer sandbox, so full host compromise would require chaining a separate sandbox escape. Chromium rates the issue High severity, the vendor has published a fix in 155.0.8059.39, and no public exploit code has been identified at time of analysis; there is no CISA KEV confirmation of active exploitation.
Remote code execution confined to Chrome's renderer sandbox is possible in Google Chrome prior to 155.0.8059.39, where a use-after-free in the browser's Bindings layer can be triggered when a victim opens a crafted HTML page. The attack is unauthenticated (PR:N) but depends on user interaction (UI:R), and because the assessed scope is unchanged (S:U), code execution is contained inside the renderer sandbox - reaching the host would require a separate sandbox-escape vulnerability. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Chrome's automatic update mechanism narrows the realistic exposure window, making this a high-priority patch item rather than an emergency.
Incorrect authorization in Google Chrome's FileSystem component allows a remote attacker to break out of the browser sandbox and potentially execute arbitrary code at the operating system level on desktop builds prior to 155.0.8059.39. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6), no authentication or prior privileges are required, but exploitation is not automatic: the attacker must use social engineering to convince the victim to open a crafted HTML page, which aligns with CISA's SSVC rating of "not automatable" and a technical impact of "total" given the scope change across the sandbox boundary. There is no CISA KEV listing and no public exploit code identified at time of analysis, and a vendor patch is available, so this should be treated as a high-severity, patch-now issue rather than an actively exploited emergency.
Out-of-sandbox code execution is achievable in Google Chrome desktop builds prior to 155.0.8059.39 by exploiting a use-after-free in the browser-process TabStrip component, reached when a victim is socially engineered into opening an attacker-crafted HTML page. The flaw carries a 9.6 CVSS (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) because the corrupted component sits outside the renderer sandbox, so a successful exploit escapes Chrome's primary containment boundary; however, it is not a zero-click bug and no public exploit identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' with Automatable 'no'. A vendor-released patch (155.0.8059.39) is available, making this a high-priority but currently non-weaponized patch-now item rather than an active incident.
Remote code execution outside the browser sandbox in Google Chrome prior to 155.0.8059.39 allows a remote attacker to execute arbitrary code on a victim's system via a crafted HTML page. The flaw is a use-after-free in the browser's Core component, and exploitation requires the victim to open attacker-controlled web content (UI:R) while no authentication or special privileges are needed (PR:N); the CVSS score is 9.6 with scope change (S:C) reflecting sandbox escape. Despite the high impact, there are no exploitation signals: no public exploit identified at time of analysis and the SSVC assessment lists exploitation as none, though the total technical impact and wide deployment make timely patching a priority.
Use-after-free in Google Chrome's Storage component (all versions prior to 155.0.8059.39) allows a remote attacker to execute arbitrary code outside the sandbox, but only after the attacker has already compromised the renderer process - typically by chaining a separate renderer bug - and only when a victim loads a crafted HTML page (CVSS 8.3, AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H). Because a prior renderer compromise, user interaction, and non-trivial heap grooming are all required, this is a second-stage sandbox-escape primitive rather than standalone initial access. No public exploit code has been identified at time of analysis, CISA SSVC records exploitation as none, and Google has shipped a vendor patch in Chrome 155.0.8059.39.
Remote code execution inside the Chrome renderer sandbox is possible in Google Chrome versions prior to 155.0.8059.39 through a race condition in the V8 JavaScript engine, triggered when a victim loads a crafted HTML page. The flaw requires no authentication (PR:N) but does require user interaction (UI:R) and depends on winning a non-deterministic timing window, which is reflected in the assessed AC:H and makes reliable exploitation harder. Resulting code execution stays within the renderer sandbox, so escaping to the host OS would require chaining a separate sandbox-escape vulnerability; no public exploit code has been identified at time of analysis, and vendor patches are available.
Use-after-free in Google Chrome's parser allows remote attackers to execute arbitrary code within the browser's renderer sandbox by convincing a victim to visit a crafted HTML page. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires user interaction (UI:R) but no authentication (PR:N). The flaw carries a High Chromium severity rating (CVSS 8.8) and no public exploit has been identified at time of analysis; however, standalone impact is constrained because the description specifies code execution 'inside the sandbox,' meaning a second vulnerability would be needed to escape to the host.
A use-after-free in the Chrome Tabs component of Google Chrome on macOS allows a remote attacker to potentially execute arbitrary code outside the sandbox when a victim loads a crafted HTML page, affecting all builds prior to 155.0.8059.39. Exploitation is unauthenticated (CVSS PR:N) but requires user interaction (UI:R) - the victim must navigate to or open attacker-controlled web content, with no zero-click vector indicated, and reliable code execution additionally depends on successful heap grooming of the freed object. The issue is assessed as a genuine high-priority problem rather than a high-CVSS-but-low-real-risk case (CVSS 9.6, scope-changed), and no public exploit was identified at time of analysis; a vendor patch is available in Chrome 155.0.8059.39.
Use-after-free in Chrome's Tint shader compiler lets a remote attacker achieve code execution outside the browser sandbox when a victim opens a crafted HTML page - the page drives Chrome's WebGPU pipeline so that Tint compiles a malicious WGSL shader that triggers the memory-safety flaw. The flaw affects Google Chrome builds prior to 155.0.8059.39 and is rated 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), with the scope-change sub-score reflecting that successful exploitation escapes the renderer sandbox and yields host-level impact; no authentication is needed, but the attacker must convince the user to visit the page (UI:R). No public exploit code has been identified at time of analysis and CISA's SSVC assessment records no exploitation, so this is currently a high-priority patch-now issue rather than an actively exploited one; a vendor patch is available in the 155.0.8059.39 stable release.
Out-of-sandbox code execution in Google Chrome for iOS (versions prior to 155.0.8059.39) stems from a missing authorization check that lets a remote, unauthenticated attacker who socially engineers a victim into opening a crafted HTML page run arbitrary code outside the browser sandbox (CVSS 3.1 base 9.6, AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, CWE-862). Exploitation is not possible without user interaction - the victim must navigate to or open attacker-controlled content on a vulnerable iOS Chrome build - and no public exploit code was identified at time of analysis, with no KEV confirmation of active exploitation. The combination of a scope-changing sandbox escape with high confidentiality, integrity, and availability impact makes this a high-priority browser flaw, but the mandatory user interaction and the narrow affected population (only unpatched iOS Chrome builds) keep it short of an emergency-patch situation.
Use-after-free in the ANGLE graphics layer of Google Chrome allows a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page; the vulnerable code path is present in Chrome builds prior to 155.0.8059.39. Exploitation is not automatic - the attacker must lure the user into rendering the malicious page (UI:R), but no credentials are required and the assessed CVSS:3.1 vector scores 9.6 with a scope change (S:C) because successful exploitation escapes Chrome's primary containment boundary rather than staying inside the renderer sandbox. Only publicly available exploit code would normally elevate this beyond an urgent patch-now item: at the time of analysis there is no indication of confirmed active exploitation (no CISA KEV listing) and no public exploit identified, while a vendor patch is available. Note that the description scopes the flaw to Chrome on Android, whereas the only vendor reference is the Desktop stable-channel release notes - the affected platform should be verified against the vendor advisory before relying on a platform-specific assumption.
Sandbox escape in Google Chrome versions prior to 155.0.8059.39: a race condition (CWE-362) in the browser's font handling can be triggered when a victim renders a crafted HTML page, potentially allowing a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox. Exploitation requires the target to load or view the attacker-controlled page (UI:R) and depends on winning a timing-sensitive race (AC:H), which typically demands repeated attempts and precise memory grooming, making this a credible high-priority browser flaw rather than a confirmed emergency. No publicly available exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and a vendor patch is available from Google.
An integer overflow in the WebGL implementation of Google Chrome on Android lets a remote attacker potentially execute arbitrary code outside the browser sandbox on devices running any build prior to 155.0.8059.39. The CVSS 3.1 base score is 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), meaning exploitation is unauthenticated but requires the victim to open an attacker-controlled HTML page that exercises the vulnerable WebGL code path; the scope change (S:C) reflects the potential escape from Chrome's renderer sandbox rather than a mere renderer crash. At time of analysis there is no public exploit identified, CISA's SSVC assessment records Exploitation: none and Automatable: no, and a vendor patch exists, so the issue is high priority on impact and patch urgency rather than on observed exploitation. Because WebGL is enabled by default on Android Chrome, no special configuration is needed on the victim side beyond navigation to the malicious page.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where a timing-dependent race condition (CWE-367) in the Core component can be won to break out of the renderer's sandbox. Exploitation is conditional rather than a single remote shot: the attacker must already have compromised the renderer process, must socially engineer the victim into opening and interacting with a crafted HTML page (UI:R), and must win a non-deterministic race that the AC:H rating and CISA's SSVC assessment (Exploitation: none, Automatable: no) indicate is unreliable and not readily scriptable. No public exploit code has been identified at time of analysis, and Google has shipped a fixed build, 155.0.8059.39; because the mandatory pre-existing renderer compromise is a high bar, this is best treated as a conditional priority to be handled through normal patching cadence rather than an emergency.
A race condition in Google Chrome's Fonts component prior to version 155.0.8059.39 lets a remote attacker escape the browser sandbox and execute arbitrary code at the browser's privilege level, but only after the attacker has already compromised a sandboxed renderer process through some separate, unrelated vulnerability. The exploit additionally requires the victim to load a crafted HTML page (UI:R) and the attacker to win a timing-dependent race (AC:H), so this is best understood as a sandbox-escape primitive rather than a standalone initial-access vector. There is no public exploit identified at time of analysis - CISA's SSVC assessment rates exploitation as 'none' and the flaw as not automatable - and a vendor-released patch (155.0.8059.39) is available, making this a high-priority defense-in-depth fix rather than a catastrophic unpatched bug.
Type confusion in ANGLE, Chrome's OpenGL ES abstraction layer, lets a remote attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox in Google Chrome versions prior to 155.0.8059.39. The victim must load attacker-controlled graphics content (crafted HTML invoking WebGL/ANGLE paths), so user interaction is required, and the bug cannot be triggered by merely visiting a page without a separate renderer exploit first - it is a second-stage sandbox-escape primitive in a multi-bug chain rather than an initial-access vector. No public exploit identified at time of analysis; CISA's SSVC assessment rates exploitation as none and automatable as no, but technical impact as total, consistent with the CVSS scope change (S:C), high confidentiality and integrity impact, and the High Chromium security severity rating.
Incorrect authorization (CWE-863) in Google Chrome's SiteIsolation component allows an unauthenticated remote attacker to execute arbitrary code in the browser when a victim loads a crafted HTML page, a flaw Google rates High and that carries a CVSS base score of 9.6. Exploitation is limited by the required user interaction (UI:R) - the victim must visit attacker-controlled or compromised web content on a build older than 155.0.8059.39 - so delivery hinges on drive-by browsing or social engineering rather than unattended compromise, consistent with CISA's SSVC rating of non-automatable. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in Chrome 155.0.8059.39.
Use-after-free in Google Chrome's Track component (versions prior to 155.0.8059.39) allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox when a victim loads a crafted HTML page. The flaw carries a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning it is network-reachable, low-complexity, and requires no authentication, with mandatory user interaction - the victim must navigate to or be redirected to attacker-controlled content - as the only gating prerequisite. Google rates the issue Critical and shipped a fix in the 155.0.8059.39 stable-channel release; no public exploit code has been identified at time of analysis, and the escape from the browser sandbox would require a separate, independent vulnerability.
Memory corruption in Google Chrome's Navigation component - a use-after-free (CWE-416) - allows a remote attacker to execute arbitrary code outside the browser sandbox on any Chrome installation prior to 155.0.8059.39 by getting a user to load a crafted HTML page. The flaw is rated Critical by Chromium with a CVSS 3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H): no authentication is required and delivery is network-based, but exploitation still depends on the victim rendering attacker-controlled content, and the scope change (S:C) reflects that successful exploitation escapes the renderer sandbox to affect the host system. No public exploit has been identified at time of analysis (CISA SSVC Exploitation: none, Automatable: no), and this is a genuine high-priority issue rather than an inflated high-CVSS score.
Use-after-free in the browser-process component of Google Chrome before 155.0.8059.39 lets a remote attacker execute arbitrary code outside the sandbox when a victim opens a crafted HTML page. Exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N) but requires the user to navigate to attacker-controlled content (UI:R); the scope change and high confidentiality, integrity, and availability ratings reflect that a successful page load escapes the renderer sandbox to reach host-level code execution, which pushes the base score to 9.6 and earns a Chromium security severity of Critical. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV, so the practical near-term risk comes from the low complexity of the trigger (phishing, malvertising, or a compromised site) rather than from observed attacks. Vendor-released patch: Chrome 155.0.8059.39.
Remote code execution outside the browser sandbox is possible in Google Chrome builds prior to 155.0.8059.39 through a use-after-free flaw in the built-in Chromecast (Cast) component: an attacker who gets a victim to render a crafted HTML page can corrupt freed memory and run arbitrary code with the browser's privileges (CVSS 9.6, Chromium severity Critical). The sole hard prerequisite is user interaction - no credentials or elevated privileges are required per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) - and because Cast ships with standard desktop Chrome rather than as an optional extension, the exposed population is essentially every unpatched Chrome installation. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google has released a fixed build.
A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an attacker within Bluetooth radio range execute arbitrary code on unpatched Android devices, with no user interaction and no additional execution privileges required. The flaw is rated CVSS 9.8 under the vendor's AV:N vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); our independent assessment re-scores it AV:A because exploitation realistically requires the device's Bluetooth to be enabled and the attacker to be within radio range to deliver crafted CCC/GATT traffic, while agreeing that no authentication or victim action limits the attack. No public exploit code and no confirmed in-the-wild exploitation have been identified at time of analysis, and a fix is published in the Android/Pixel security bulletin dated 2026-10-01.
Path traversal in Dell System Update (DSU) versions prior to 2.3.0.0 allows an unauthenticated remote attacker to escape the intended restricted directory when the DSU client processes crafted pathnames in update content, resulting in filesystem access. Because DSU operates with elevated privileges, exploited path traversal can escalate to arbitrary code execution as root, potentially compromising both the application and the underlying operating system. Exploitation is not automatic: the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) shows remote, unauthenticated reach but a mandatory user interaction step, and no public exploit code was identified at time of analysis. Dell has published a fixed release, and this is a genuinely high-priority flaw rather than merely a high-CVSS outlier.
Remote code execution in Payload CMS before 3.90.0 (and canary builds before 4.0.0-canary.34) lets a remote, unauthenticated attacker execute arbitrary code by sending a crafted request to the public first-register operation. The flaw only applies to instances that have local authentication enabled and have not yet had their first admin user created, i.e. a freshly deployed, re-provisioned, or ephemeral instance still inside its initial setup window; once an admin exists the attack surface disappears. No public exploit identified at time of analysis, and no evidence of active exploitation (not in CISA KEV), though the CVSS 8.1 score with full confidentiality, integrity and availability impact makes this a high-priority fix for anyone running uninitialized deployments.
Unauthorized read access to stored form submissions and form email configuration in Payload CMS deployments running the @payloadcms/plugin-form-builder plugin before 3.90.0 (and 4.0.0-canary versions before 4.0.0-canary.34) is achievable by an authenticated non-admin user, based on the vendor patch, which replaces a permissive 'any logged-in user' read rule with a check that the requester belongs to the configured admin user collection. The published CVE record characterizes the flaw as remote code execution (CWE-94, CVSS 10.0), but the actual shipped fix is an access-control tightening on the Forms and FormSubmissions collections plus tests asserting that users from unrelated collections are denied, so the verifiable impact is a confidentiality breach of form data rather than code execution; these conflicting signals should be reconciled with the vendor advisory before prioritization. There is no public exploit identified at time of analysis and no indication of confirmed active exploitation, but the authorization requirements (the CVSS vector claims unauthenticated, while the patch implies a logged-in non-admin account is needed) should be confirmed against the vendor before assuming unauthenticated exposure.
Unauthenticated remote code execution in the SPIP Crayons plugin before 3.5.0 allows any remote attacker to take over a SPIP site by reaching crayons_store.php without the secu_ anti-forgery parameter, which causes the authorization dispatcher to select an unconditionally-true handler instead of the legitimate modification check. With authorization bypassed, the attacker can write an arbitrary .html skeleton file, read configuration files that expose the site secret, and forge a signed AJAX context that executes the planted skeleton as PHP under the web-server user. The assessed impact is high across confidentiality, integrity, and availability (CVSS:3.1 AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H; vendor-scored 9.3), exploitation requires only that the Crayons plugin be installed and enabled below 3.5.0, and no public exploit code was identified at time of analysis though the flaw is trivially reachable and unauthenticated.
Prototype pollution in Payload CMS's @payloadcms/plugin-import-export module lets an unauthenticated remote attacker submit prototype-sensitive field paths to the plugin's endpoints, corrupting object prototypes and triggering unintended application behavior that can escalate to remote code execution. The flaw affects Payload 3.0.0 through versions before 3.88.0 and 4.0.0-canary.0 through versions before 4.0.0-canary.27, but only when the Import Export plugin is installed and enabled - sites without that plugin are unaffected. No public exploit code has been identified at time of analysis, and exploitation is gated by the presence of a reachable prototype-pollution gadget in the target application, so real-world impact is conditional even though the vendor advisory and a 9.3 CVSS 4.0 score (independent assessment: CVSS 3.1 8.1-range with AC:H) both flag it as high severity.
HortusFox versions before 6.2 expose an authenticated remote code execution path through the theme import feature (ThemeModule::startImport): an uploaded ZIP archive is extracted into the public web root before file names, extensions, or content are validated, so an attacker with an administrator account can bundle a PHP payload and an .htaccess file that re-enables PHP execution and then execute arbitrary OS commands as the web-server user by requesting the dropped file under the themes directory. Exploitation is gated by administrator privileges (CVSS PR:H), so practical risk depends on obtaining or compromising an admin account; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV). The vendor addressed the flaw in the 6.2 release, and the issue is tracked under CWE-434 (unrestricted upload of a file with a dangerous type).
Openapi-python-client before 0.29.1 fails to neutralize attacker-influenced content from an OpenAPI document when rendering string, docstring, and f-string contexts, so a malicious or untrusted specification can cause arbitrary Python to be emitted into the generated client - code that then executes when that client is imported, compromising the integrity of the importing environment and potentially its confidentiality and availability. Exposure is conditional: it requires someone to generate a client from a spec they do not fully control (a third-party, public, or otherwise untrusted API definition) and then import the generated code, which is the trigger point, so organizations generating only from trusted internal specs are effectively unaffected. The flaw is rated 8.4 under CVSS 4.0 in the source data (independent assessment maps it to CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), which is consistent with a serious but conditionally triggered supply-chain and code-generation issue rather than a remotely reachable mass-exploitation vector. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has shipped a fix in version 0.29.1.
Code injection in Microsoft Kiota 0.5.0 through pre-1.35.0 allows attacker-controlled text embedded in an OpenAPI description to break out of the generated Java or PHP documentation comment and execute in the consuming application or build environment once that generated source is compiled and loaded (Java) or loaded (PHP). The flaw is reachable unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction: a developer or CI pipeline must generate client code from an untrusted or tampered spec and then build or load the output, making this a build-time/supply-chain path rather than an attack on already-deployed runtime services. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV; CVSS 3.1 base score is 8.8, and the issue is fixed in 1.35.0.
Heap buffer overflow in libmikmod's Oktalyzer (.okt) loader lets a crafted module corrupt heap memory and potentially achieve code execution, because a 16-bit track-count field (numtrk = numpat * numchn) can be made to wrap while pattern data is still written for the full, unwrapped track count. Any application linked against libmikmod before 3.3.14 is affected, and exploitation requires the victim to open or otherwise process an attacker-supplied .okt file, matching the independently assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R (7.8) rather than a remotely reachable condition. No public exploit identified at time of analysis, and the 3.3.14 release rejects overflowing track counts outright.
Heap buffer overflow in libmikmod before 3.3.14 is triggered when an application linked against the library parses a crafted DSM module whose numchn and numpat header fields produce a product that overflows the 16-bit UWORD truncation in DSM_Load(), corrupting heap memory and potentially enabling code execution. The issue is local and file-based: an attacker must deliver a malicious DSM file and a victim must open or play it, so it is not a drive-by remote threat; no authentication or special privileges are required, and no public exploit has been identified at time of analysis. A vendor-released patch is available in libmikmod 3.3.14.
PHP code injection in the Smarty templating engine allows remote code execution in applications running Smarty 4.x before 4.5.8 or 5.x before 5.8.5 that render templates through the extends:/multi-component inheritance path with caching enabled. When such a template is compiled, the top-level unifunc never restores its nocache_hash, so the value is null; combined with an empty regex alternative in the cache-split logic, attacker-controlled assigned data containing a forged /*%%SmartyNocache:%%*/ marker is copied verbatim (bypassing PHP-tag neutralization) into the regenerated PHP cache file and executed on the next include. Exploitation is unauthenticated per the vendor CVSS vector (PR:N) but is gated by strict preconditions - inheritance-path templates, active caching, unescaped attacker-controlled output, and a fresh PHP process that reloads the compiled file after the cache entry is evicted (TTL expiry or cache clear) while compiled files persist - making it conditional rather than reliably on-demand; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis.
Insecure deserialization in the TrueLayer Magento 2 Plugin's Psr16CacheAdapter component allows an attacker who already has write access to the Magento cache backend (Redis or Memcached) to achieve arbitrary code execution via crafted PHP objects. The flaw arises from PHP's unserialize() being called without class restrictions, and exploitation requires both cache-write capability-obtainable through local filesystem access or an exposed cache service-and the presence of a usable gadget chain in the deployed Magento/Adobe Commerce environment. Although rated CVSS 7.5, real-world risk is materially lower because the attack preconditions are stringent; no public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited.
Authenticated remote code execution in Craft CMS 5.10.13.2 allows any low-privilege Control Panel user to run operating-system commands as the PHP/web-server process by injecting Twig through the app/render-components action. The attack requires only basic CP access; a non-admin Team user with no optional permissions was shown to override an EntryType uiLabelFormat and trigger an Entry render that evaluates attacker-controlled Twig via renderObjectTemplate(). No public exploit identified at time of analysis, but the impact is severe because the render path is unsandboxed and can reach PHP functions such as system().
Remote code execution (RCE) in WPShopmart Tabs Responsive plugin for WordPress (versions <= 2.5) allows an authenticated attacker with Editor-level privileges to execute arbitrary code on the server. This high-severity vulnerability (CVSS 8.0, CWE-94) requires high-complexity conditions (AC:H) and no user interaction (UI:N). No public exploit code has been identified at time of analysis; risk is concentrated on multi-user sites where untrusted users have elevated editing roles.
Remote code execution in WooCommerce Designer Pro (versions up to 1.9.33) allows authenticated attackers with Subscriber-level access or higher to execute arbitrary code on the server. The flaw is a code injection (CWE-94) with a CVSS score of 9.9 (Critical), requiring no user interaction and resulting in complete loss of confidentiality, integrity, and availability (scope change). Exploitation is most realistic on WooCommerce storefronts that permit open customer self-registration; no public exploit identified at time of analysis. The independent assessment confirms this is a genuine high-priority issue rather than a theoretical risk.
Remote code execution in the ACPT (Premium) WordPress plugin affects all versions up to and including 2.0.66, allowing an authenticated attacker with only subscriber-level access to run arbitrary code on the server. The chain works by abusing a REST API form-creation endpoint that performs no capability check, planting a malicious email_settings payload, and then triggering a form submission so the plugin's unsandboxed Twig environment renders attacker-controlled template expressions during email generation. No user interaction is required and no public exploit code has been identified at time of analysis, though the low authentication bar (subscriber) makes it considerably more dangerous on sites with open registration; exploitation is not confirmed actively exploited (no CISA KEV listing), and the vendor changelog points to a fixed release.
Remote code execution in Immich before 3.2.4 lets any authenticated non-admin user with upload permission run arbitrary code inside the immich-server container. The exploit chains two crafted SVG assets: a stored reference asset and a second 'delayed-marker' SVG whose attacker-controlled <image href> value reaches ImageMagick's unrestricted MSL and VIDEO coders after the file bypasses libvips' native SVG loader, with execution occurring when the server generates a thumbnail. The attack is high-complexity and depends on the ImageMagick fallback path being reachable with those coders enabled; version 3.2.4 contains the fix, and no public exploit code was identified at time of analysis.
Unauthorized code execution during the boot process is possible on AMD Zynq UltraScale+ MPSoC, Zynq UltraScale+ RFSoC, and Kria SOM devices when an attacker with physical or local USB access can drive oversized Device Firmware Upgrade (DFU) download requests while the device is held in USB boot mode. The flaw is an out-of-bounds write (CWE-787) in the USB boot-mode DFU path: missing boundary validation allows the download to overflow the DDR receive buffer and corrupt adjacent First Stage Boot Loader (FSBL) memory before the FSBL hands off to later boot stages. AMD rates this 7.5 (CVSS 4.0 AV:L/AC:L/AT:P/PR:N/UI:N with High confidentiality, integrity, and availability impact to the device); no public exploit code and no confirmed active exploitation were identified at time of analysis, and practical exposure is limited to devices whose boot configuration actually permits USB boot rather than QSPI/eMMC/SD.
Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.
Authenticated users of Langflow versions prior to 1.9.0 can achieve remote code execution on the underlying host by adding an MCP server that uses the Stdio transport, because the user-supplied command field is passed directly to a shell with no validation, allowlisting, or sandboxing; the injected command executes immediately when the MCP server list is fetched, requiring no further victim interaction, and the env field additionally permits environment-variable injection (for example LD_PRELOAD or PATH overrides) for a second code-execution path. The vendor has issued a fix in 1.9.0 that restricts MCP stdio commands to an allowlist and blocks dangerous environment variables, and no public exploit code has been identified at time of analysis. The 9.9 CVSS score reflects the vector's scope change (S:C) and high confidentiality, integrity, and availability impact, though practical exploitability depends on the attacker holding a valid authenticated Langflow account with access to MCP server configuration.
Code execution in Newell Brands DYMO ID 1.5.1.71 occurs because the application resolves its plugin Modules directory relative to the process working directory, letting an attacker who places a malicious plugin module or DLL alongside a crafted job file load arbitrary code at the victim's privilege level once that job file is opened. The issue is local and file-delivery based rather than network-reachable, requires explicit victim interaction (opening the crafted job), and grants only the privileges the victim already holds, so it cannot self-propagate; no public exploit code and no CISA KEV entry were identified at time of analysis. The vendor has released a fix in DYMO ID 1.6.0.
Authenticated Ghost Administrators on versions 6.10.3 through 6.63.x can achieve remote code execution by installing a crafted theme that abuses how Ghost resolves theme translation (i18n) files, allowing path traversal into attacker-controlled code. Exploitation requires a high-privilege Administrator account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) and no victim interaction beyond the attacker's own admin actions; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Because the attacker population is limited to trusted or already-compromised admin accounts rather than anonymous remote users, this is a high-severity but access-gated issue rather than a mass-exploitation priority.
Remote code execution in Ghost CMS 6.56.0 through 6.66.x lets any authenticated staff user - including the lowest-privilege Contributor role - execute arbitrary commands on the Ghost server by creating a bookmark card that points to an attacker-controlled website serving a crafted SVG. The root cause is a code-injection flaw (CWE-94) in the SVG handling path of an image-processing library bundled with Ghost, and successful exploitation yields full confidentiality, integrity, and availability impact on the host. Exploitation requires a valid Ghost staff login (the vendor vector claims PR:N, but our assessed vector of PR:L/UI:N is the accurate prerequisite), and there is no public exploit identified at time of analysis. Ghost 6.67.0 is the fixed release.
Code execution via local privilege escalation is possible in Google Android's Bluetooth AVRCP handling (handle_app_val_response in btif_rc.cc) because of a race condition (CWE-362) that can corrupt shared state in the Bluetooth stack. The flaw is rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N) and affects Android 16, Android 16-qpr2, and Android 17; an attacker must already have a low-privilege app installed on the device and must repeatedly drive the AVRCP remote-control code path to win a narrow timing window, with no user interaction required. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, so while the technical impact is total if the race is won, the high attack complexity and local-only prerequisites keep this a lower-urgency item than a remotely reachable, deterministic bug.
Heap-based out-of-bounds write in Android's Bluetooth stack, specifically the cfg2prop routine in btif_storage.cc, can be triggered when the Bluetooth subsystem converts attacker-influenced bonded/stored device configuration data into Bluetooth properties, potentially leading to remote code execution. Affected builds are Android 16, Android 16-qpr2, and Android 17; the assessed vector requires low privileges (PR:L, consistent with a pairing/component-level context) and no user interaction, and real-world reachability is expected to be radio-adjacent (a nearby, paired, or spoofed Bluetooth device) rather than arbitrary internet access, even though the vendor-assigned vector carries AV:N. No public exploit code has been identified and SSVC records exploitation as none at time of analysis, but the flaw is memory-corruption class with total technical impact, so it warrants priority patching on devices where Bluetooth is enabled and pairing is common.
Integer overflow in the Media component of Google Chrome (all versions prior to 155.0.8059.39) allows a remote, unauthenticated attacker to corrupt memory via a crafted HTML page containing specially formed media content, with the potential to execute arbitrary code outside the browser sandbox. Exploitation is not automatic: the CVSS vector (UI:R) confirms the victim must actively load the attacker-controlled or compromised page, and Google rated this a Chromium severity of 'Low', indicating the sandbox-escape outcome is not reliably achievable and probably depends on specific memory conditions or combining this primitive with others. No public exploit code and no CISA KEV entry were identified at time of analysis; the 9.6 score reflects the scope-change metric (S:C) and high C/I/A impact rather than proven real-world exploitation, so the practical risk is lower than the headline score suggests.
Sandbox escape in Google Chrome before 155.0.8059.39 via a heap-based buffer overflow (CWE-122) in ANGLE, Chrome's graphics translation layer: a remote attacker who has already compromised a sandboxed renderer process can use a crafted HTML page to execute arbitrary code outside the sandbox. It is a second-stage primitive rather than an initial-access bug - the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H (8.3) reflects high attack complexity, a required pre-existing renderer exploit chain, and active user interaction (UI:R), with the scope change S:C capturing the crossing of the sandbox boundary, even though Chromium rates the underlying bug Low severity. No public exploit code was identified at time of analysis and CISA's SSVC data records no observed exploitation, so the headline 8.3 should be weighed against the significant preconditions.
Code execution outside the Chrome sandbox on Windows is possible through CVE-2026-106186, an uncontrolled search path flaw in Chrome's CredentialProvider component affecting Chrome builds prior to 155.0.8059.39. The issue is local-only (CVSS:3.1/AV:L) and requires both a pre-existing local foothold with write access to a directory the component searches and user interaction to load the affected program, yet because the credential provider loads in a more privileged Windows context the scope changes (S:C) and confidentiality, integrity, and availability impacts are all High, yielding a base score of 8.6 with no privileges required (PR:N). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; SSVC rates exploitation as 'none' and automatable as 'no', and Chromium's own internal severity rating is 'Low', which sharply tempers the headline CVSS figure. A vendor patch is available as Chrome 155.0.8059.39.
Arbitrary code execution confined to Chrome's renderer sandbox is possible in Google Chrome versions prior to 155.0.8059.39, where an incorrect comparison in the font rendering pipeline can be triggered by a crafted HTML page. This is an unauthenticated remote attack (AV:N/PR:N) that requires the victim to load attacker-controlled web content (UI:R); the resulting code execution stays inside the renderer sandbox (S:U), and escaping to the host operating system requires a separate, unrelated sandbox-escape vulnerability - which is why Chromium assigned a Low security severity despite the CVSS 8.8 base score. No public exploit code was identified at time of analysis, and a vendor-released patch (155.0.8059.39) is available.
Missing authorization in the Actor component of Google Chrome prior to 155.0.8059.39 allows code to escape the browser sandbox, but only after the attacker has already compromised the renderer process via a separate bug and then gets the victim to load a crafted HTML page. This prerequisite, combined with required user interaction (UI:R) and high attack complexity (AC:H) from the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H vector, means the flaw is only usable as a link in an exploit chain rather than as a standalone initial-access vector; the changed scope (S:C) and high confidentiality, integrity and availability impact reflect the potential for full code execution outside the sandbox. No public exploit code identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status, so risk should be weighed against the conflicting 8.3 score versus the demanding exploitation preconditions. A vendor patch is available in Chrome 155.0.8059.39.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where incorrect reference resolution in the WebAppInstalls component allows crafted network traffic to cross a process trust boundary. Exploitation is not standalone: the attacker must already have compromised the Chrome renderer process, which makes this a second-stage sandbox-escape primitive in a larger exploit chain rather than a directly reachable remote compromise, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects that non-trivial precondition. A vendor-released patch (Chrome 155.0.8059.39) is available, and no public exploit code was identified at the time of analysis.
Type confusion in V8, Chrome's default JavaScript and WebAssembly engine, enables a remote attacker to run arbitrary code inside the browser's renderer sandbox in Google Chrome releases below 155.0.8059.39. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms the attack is network-reachable and requires no authentication, though it does require the victim to open attacker-controlled web content, so a phishing, malvertising, or watering-hole lure is a prerequisite. No public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as 'none' and the issue as not automatable, so real-world priority currently sits below what the 8.8 base score alone implies; note that code execution is confined to the renderer sandbox, meaning full host compromise would require chaining a separate sandbox-escape flaw. Google has shipped a vendor patch.
Incorrect authorization in the Google Chrome user-interface layer allows a crafted HTML page to escape the renderer sandbox and execute arbitrary code outside it on all Chrome builds prior to 155.0.8059.39. Exploitation requires the victim to open an attacker-supplied page (UI:R in the assessed vector) and, while no authentication is required (PR:N) and no unusual configuration is needed, the attack is not fully remote - it depends on that user action, which is the main limiting factor. Severity signals are mixed: the assessed CVSS vector scores 9.6 with scope change (S:C) and high confidentiality, integrity and availability impact, yet Google rates the underlying Chromium issue as Medium, and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Arbitrary code execution inside the Chrome renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a race condition (CWE-367) in the V8 JavaScript engine can be won by a crafted HTML page. Exploitation requires only that the victim load the attacker's page in a vulnerable browser (UI:R, PR:N per the CVSS vector), with no credentials or prior privileges needed, but success additionally depends on hitting a time-of-check/time-of-use timing window, which our assessment captures by raising attack complexity to High (CVSS 3.1 base 8.1 under AC:H, versus the 8.8 score supplied with the CVE under AC:L). The critical caveat is scope: the code execution achieved stays within the renderer sandbox and does not by itself compromise the host operating system, so full system impact requires chaining a separate sandbox-escape vulnerability. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none (Automatable: no, Technical Impact: total), and a vendor-released patch exists in Chrome 155.0.8059.39.
An out-of-bounds write in the Media component of Google Chrome before 155.0.8059.39 lets a remote attacker corrupt memory and potentially achieve arbitrary code execution outside the browser sandbox when a victim opens an attacker-crafted HTML page containing malicious media content. The attack is fully remote and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N), but it is gated by user interaction (UI:R) - the victim must visit the malicious or compromised page - and the 'outside the sandbox' outcome implies defeating Chrome's process sandbox, which is materially harder in practice than the 9.6 base score suggests. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fixed build.
Incomplete cleanup in Dawn, Chrome's WebGPU implementation, allows a crafted HTML page to potentially corrupt GPU-process state and achieve code execution outside the browser sandbox in Google Chrome builds prior to 155.0.8059.39. Exploitation requires the victim to render attacker-controlled content that reaches the affected WebGPU/Dawn code path (CVSS UI:R with PR:N - unauthenticated remote attackers, but user interaction required), and the outcome is probabilistic rather than a guaranteed silent drive-by; the published base score is 9.6 while Google rates the issue Medium, and our assessed vector raises attack complexity to AC:H to reflect the difficulty of chaining a cleanup flaw into a reliable sandbox escape. No public exploit code has been identified at time of analysis, and Google has released Chrome 155.0.8059.39 as the fix.
Heap-based buffer overflow in Google Chrome's font-handling code (CWE-122) lets an attacker who has already compromised the renderer process execute arbitrary code outside the sandbox when a victim renders a crafted HTML page containing malicious font data. All Chrome builds prior to 155.0.8059.39 on default configurations are affected; exploitation is unauthenticated (PR:N) but requires user interaction (UI:R) and a pre-existing renderer compromise, so it functions as a sandbox-escape chain component rather than a standalone drive-by, and is rated high complexity (AC:H) despite a CVSS base of 8.3 (S:C). No public exploit code has been identified at time of analysis and CISA's SSVC assessment records no exploitation, but the vendor has shipped a fix in 155.0.8059.39.
Use-after-free in Chrome's font handling on Windows allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page; the flaw affects Google Chrome versions prior to 155.0.8059.39. Exploitation requires user interaction (UI:R) - the victim must load attacker-controlled content - and there are no authentication prerequisites (PR:N), but the resulting code execution is confined to the Chrome sandbox, so host-level compromise would require a second, independent sandbox-escape bug. Consistent with the medium severity rating assigned by the Chromium team, CISA's SSVC assessment records no known exploitation and no automatable exploitation path, and no public exploit code has been identified at time of analysis.
Arbitrary code execution outside Chrome's sandbox on Android affects Google Chrome builds prior to 155.0.8059.39, where a missing authorization check (CWE-862) can be abused by a malicious co-installed Android app. The attack is local - it requires an attacker-controlled app to already be present on the same device plus successful social engineering to get the victim to install it and trigger the action - so a default, lone Chrome installation is not directly exploitable. Google rates this Chromium security severity Medium, the vendor CVSS is 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our assessment substitutes UI:R, no publicly available exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is only 0.12% (2nd percentile).
Sandbox escape and potential arbitrary code execution outside the browser sandbox in Google Chrome via a confused-deputy flaw in the Google Lens feature, affecting all desktop releases prior to 155.0.8059.39. Exploitation is not standalone: a remote attacker must first have compromised the Chrome renderer process (a separate renderer-stage bug), then convince the victim to load a crafted HTML page, after which the Lens component can be induced to perform a privileged operation that crosses the sandbox boundary on the renderer's behalf - consistent with the CVSS:3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H and high attack complexity. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV absent, SSVC exploitation: none), but the maximum technical impact rating means the issue is worth prioritizing within normal patch cycles; vendor-released patch: 155.0.8059.39.
Race condition in the V8 JavaScript engine allows remote code execution inside the browser sandbox in Google Chrome builds prior to 155.0.8059.39. A remote, unauthenticated attacker can trigger the flaw by getting a victim to open attacker-supplied HTML that drives V8 into the timing window (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) - the required user interaction is the only precondition, and code execution is confined to the renderer/V8 sandbox, so host compromise would require a second, separate sandbox-escape bug. Google has shipped a fixed stable-channel build, and no public exploit code or confirmed active exploitation was identified at time of analysis (CISA SSVC records Exploitation: none; no KEV listing or PoC in the available sources).
Sandbox escape in Google Chrome on iOS (versions prior to 155.0.8059.39) allows a local attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox via a local program. The flaw is an incorrect reference resolution (CWE-706) in the Passwords component, rated Medium by Chromium and carrying a CVSS 7.4 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code or confirmed active exploitation has been identified at time of analysis; a vendor patch is available.
Sandbox escape in Google Chrome on macOS, affecting releases prior to 155.0.8059.39, allows an attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox when the victim views a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, base 8.3) confirms a network-reachable, scope-changing escape that requires user interaction and carries high confidentiality, integrity and availability impact once triggered, but the AC:H rating and CISA SSVC 'Automatable: no' reflect that it cannot be used standalone - a prior renderer compromise is a hard prerequisite. Per the authoritative assessment this is a chained second-stage exploit limited to macOS; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the Mobile component of Google Chrome on iOS allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim is socially engineered into opening a crafted HTML page, fixed in Chrome 155.0.8059.39. Successful exploitation requires user interaction (CVSS vector PR:N/UI:R with S:C), meaning the attack hinges on phishing or a malicious link rather than a zero-click path, and the scope change reflects the assessed ability to escape the sandbox boundary. No public exploit code has been identified at time of analysis and the issue is not a confirmed actively exploited (CISA KEV) vulnerability, but the 9.6 CVSS score and the RCE tag make prompt patching of older mobile Chrome installations the priority.
A use-after-free memory-safety flaw in Google Chrome's Media component lets a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a user loads a crafted HTML page containing malicious media content. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires the victim to visit or load the attacker-controlled page (UI:R), which is the main practical barrier; no credentials or special privileges are needed. There is no public exploit identified at time of analysis and the CISA SSVC assessment records no exploitation, but the vendor has shipped a fix in 155.0.8059.39, and the EPSS-style risk picture is dominated by Chrome's ubiquity and the high CVSS base score (8.8) rather than by observed attacks.
Incorrect authorization in the Search component of Google Chrome for Android before 155.0.8059.39 can allow a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim is socially engineered into opening a crafted HTML page. The vendor-rated Chromium severity is Medium, yet the assessed CVSS is 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) because the flaw crosses a security boundary (scope changed) with high confidentiality, integrity and availability impact. The risk signals conflict and must be weighed carefully: the impact score is severe, but exploitation requires a click of user interaction, is confined to Android builds (desktop Chrome is unaffected), and no public exploit code or confirmed active exploitation has been identified at the time of analysis. Vendor patches are available.
Use-after-free in Google Chrome's garbage-collection code before 155.0.8059.39 allows an unauthenticated remote attacker to corrupt memory and execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (PR:N, UI:R) and the code execution stays contained in the browser sandbox, so OS-level compromise would require chaining a separate sandbox-escape flaw; no public exploit identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', which tempers the high 8.8 CVSS base score. Vendor-released patch: 155.0.8059.39, distributed through Chrome's stable channel.
Use-after-free in the Streaming component of Google Chrome prior to 155.0.8059.39 allows unauthenticated remote attackers to execute arbitrary code inside the renderer sandbox when a victim is socially engineered into loading a crafted HTML page, consistent with the CVSS vector AV:N/AC:L/PR:N/UI:R. Google rates the issue Medium severity (Chromium) while the CVSS base score is 8.8, reflecting high confidentiality, integrity, and availability impact on the renderer process rather than the host. There is no CISA KEV listing and no public exploit identified at time of analysis, and the SSVC assessment records exploitation as none; the primary containment is Chrome's process sandbox, so full host compromise would require chaining a separate sandbox-escape flaw.
Sandbox escape in Google Chrome's WebAppInstalls component allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox when a victim visits a crafted HTML page and is socially engineered into interacting with the web app installation flow. The flaw is a missing authorization check (CWE-862) affecting Chrome versions prior to 155.0.8059.39; the technical impact is total, but the vendor rates it Medium because exploitation requires a prior renderer compromise, deliberate user interaction (UI:R), and high attack complexity (AC:H) rather than a default-configuration remote hit. No public exploit code and no confirmed active exploitation have been identified at time of analysis (CISA SSVC Exploitation: none, Automatable: no).
Use-after-free in Google Chrome allows unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by convincing a victim to load a crafted HTML page, affecting all versions prior to 155.0.8059.39. The attack requires user interaction (UI:R) but no authentication or special configuration, and while code execution is confined to the sandbox, the CVSS 3.1 score is 8.8. No public exploit or active exploitation has been identified, and a vendor patch is available.
A sandbox escape in Google Chrome before 155.0.8059.39 lets an attacker who has already compromised the browser's renderer process trigger a race condition in Chrome's font handling and execute arbitrary code outside the sandbox, via a crafted HTML page the victim must load (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, score 8.3). The prerequisite is significant: a separate, prior renderer compromise is required, and AC:H reflects the non-deterministic nature of winning the race, so this is a chained post-exploitation primitive rather than a standalone drive-by. Unauthenticated from a network perspective, with UI:R meaning the target must open attacker-controlled content; no CISA KEV entry, no public exploit code identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no, though technical impact is total once the race is won. Vendor-released patch: 155.0.8059.39.
Use-after-free in Google Chrome's Track component before 155.0.8059.39 allows an unauthenticated remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The CVSS 3.1 base score is 8.8 (High) with UI:R, meaning exploitation requires user interaction but no authentication; successful code execution remains confined to Chrome's renderer sandbox and would require a separate sandbox-escape bug to affect the host OS. No public exploit identified at time of analysis, and SSVC records Exploitation: none; CISA KEV does not list this CVE.
Use-after-free in Google Chrome's built-in PDF handling (fixed in 155.0.8059.39) lets remote, unauthenticated attackers execute arbitrary code inside the Chrome renderer sandbox when a victim opens a crafted PDF file - exploitation is not automatic and depends entirely on the user interaction of opening the document (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-416). Because the code execution is confined to the sandboxed renderer, turning this into full host compromise would require chaining a separate sandbox-escape bug; the advisory rates it Chromium severity High. At the time of analysis there is no public exploit identified and CISA SSVC records exploitation as none, though the vulnerability is fully described and a vendor patch plus the underlying Chromium issue tracker entry are publicly referenced. Google Chrome versions before 155.0.8059.39 are affected on all platforms tracked under cpe:2.3:a:google:chrome.
Google Chrome builds prior to 155.0.8059.39 contain a use-after-free in PDF handling that allows a remote, unauthenticated attacker to execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page that embeds a malicious PDF. Exploitation requires the user to open attacker-controlled web content processed by Chrome's built-in PDF (PDFium) viewer - a mandatory interaction step (CVSS UI:R) with no zero-click vector, and any code execution is confined to the sandboxed renderer unless chained with a separate sandbox escape. There is no public exploit identified at time of analysis, SSVC records no observed exploitation and rates the issue not automatable, but technical impact is rated total given high confidentiality, integrity, and availability impact; a vendor patch exists in 155.0.8059.39.
Use-after-free in Google Chrome's V8 JavaScript engine (all releases prior to 155.0.8059.39) lets unauthenticated remote attackers execute arbitrary code inside the renderer sandbox when a victim navigates to an attacker-controlled page containing crafted HTML/JavaScript. The bug carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium's own 'High' severity rating, and because the V8 engine is enabled by default in every standard installation, no special configuration or privileges are needed on the target side. Impact is bounded, however: per the vendor description code execution is confined to the sandbox, so a standalone exploit does not by itself compromise the host and a separate sandbox-escape would be required, and no public exploit identified at time of analysis (SSVC Exploitation: none, Automatable: no) - a genuine priority-worthy issue whose urgency is tempered by the required user interaction, sandbox confinement, and absence of observed exploitation.
Use-after-free in the Media component of Google Chrome prior to 155.0.8059.39 lets a remote attacker execute arbitrary code within the browser's renderer sandbox by luring a victim to open a crafted HTML page. The flaw carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or prior privileges are required, but successful exploitation depends on the user actively navigating to attacker-controlled content. There is no public exploit identified at time of analysis - CISA's SSVC assessment lists exploitation as 'none' - and code execution is contained within the renderer sandbox, so a separate sandbox-escape would be needed to reach the host OS; the vendor has released a patched build.
Type confusion in the V8 JavaScript engine of Google Chrome prior to 155.0.8059.39 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page; the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, so the sole prerequisite is that the victim renders attacker-controlled content in an unpatched desktop build. No public exploit code or active exploitation was identified at time of analysis, and CISA KEV does not list this CVE. The vendor-released patch is Chrome 155.0.8059.39, and installations already updated past that version are not affected. Because the impact is scoped to the sandbox (S:U) per the description, full host compromise would require chaining a separate sandbox-escape vulnerability.
Google Chrome versions prior to 155.0.8059.39 contain a use-after-free in the WebRTC component that a remote, unauthenticated attacker can trigger by convincing a victim to visit a crafted HTML page, resulting in arbitrary code execution within the renderer sandbox (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not automatable and requires user interaction, and the resulting code execution is confined to Chrome's renderer sandbox per the vendor description, so full host compromise would additionally require chaining a separate sandbox-escape flaw. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records no known exploitation; Chrome's built-in auto-update is the primary exposure-reduction control, as patched versions 155.0.8059.39 and later are not vulnerable.
Arbitrary code execution inside the renderer sandbox is achievable in Google Chrome builds prior to 155.0.8059.39, where a use-after-free in the browser's Media component can be triggered when a victim loads a crafted HTML page. Scoring 8.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, the bug requires no authentication but does require the user to visit attacker-controlled content, and because the resulting code execution is confined to the renderer sandbox, full host compromise would require chaining a separate sandbox-escape flaw. A vendor patch is available in the Chrome Stable channel update, and no public exploit has been identified at time of analysis - this is a high-priority patching item rather than an emergency.
Arbitrary code execution confined to the renderer sandbox in Google Chrome builds prior to 155.0.8059.39, reachable when a user opens a crafted HTML page that drives the DevTools state-validation path into an inconsistent state. The flaw is network-delivered and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N), but exploitation is gated by mandatory user interaction (UI:R), which is why CISA's SSVC decision framework rates it as not automatable. No public exploit code and no confirmed active exploitation were identified at time of analysis; Google rates the Chromium severity as High and has shipped a fixed build, so the practical exposure is limited to unpatched clients that have not yet received the auto-update.
Use-after-free in Google Chrome's Media component allows a remote attacker to execute arbitrary code inside the browser's renderer sandbox by luring a victim into loading a crafted HTML page in any Chrome build prior to 155.0.8059.39. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), consistent with Google's own 'High' Chromium security severity, and requires no authentication or privileges on the victim host beyond the user visiting the malicious content (UI:R). Exploitation is confirmed to be constrained by user interaction and by the renderer sandbox - CISA SSVC scores it Exploitation: none, Automatable: no, Technical Impact: total - and there is no public exploit identified at time of analysis, though a vendor-released patch is available.
Use-after-free in Google Chrome's parser allows remote, unauthenticated attackers to execute arbitrary code inside the renderer sandbox by convincing a victim to load a crafted HTML page, affecting all Chrome versions prior to 155.0.8059.39. Exploitation requires user interaction (the victim must visit or open the malicious page), and the resulting code execution is contained by Chrome's renderer sandbox, so full host compromise would require chaining with a separate sandbox-escape vulnerability. A vendor patch is available in 155.0.8059.39, and no public exploit identified at time of analysis, with CISA's SSVC assessment recording exploitation as none.
Remote code execution inside the renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a use-after-free in the Media component can be triggered by a crafted HTML page. Exploitation requires the victim to load attacker-controlled web content (UI:R) but no authentication or special privileges (PR:N), so default desktop installs are affected; resulting code execution is contained within the renderer sandbox rather than the host operating system. At time of analysis there is no public exploit identified at time of analysis per available intelligence (SSVC exploitation: none, automatable: no), and a vendor patch is available from Google. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium security severity High, this is a genuine high-priority patching item, though the signals are mixed on urgency.
A use-after-free in Chrome's Metrics component (CWE-416) lets an attacker who has already compromised a sandboxed renderer process execute arbitrary code outside the sandbox - a sandbox-escape primitive rather than an initial-access bug. Only users running Chrome versions below 155.0.8059.39 are affected; the flaw is unauthenticated from the network perspective (PR:N) but requires the victim to load attacker-controlled crafted HTML (UI:R) and carries High attack complexity (AC:H) because the attacker must win a use-after-free race and defeat sandbox mitigations. Google has released a fix in Chrome 155.0.8059.39, no public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none, and the overall posture is patch-promptly-but-not-emergency rather than urgent.
Use-after-free in Google Chrome's Select component before version 155.0.8059.39 allows unauthenticated remote attackers to execute arbitrary code inside the browser's renderer sandbox, but only after socially engineering a victim into opening a crafted HTML page (CVSS 3.1 8.8, AV:N/AC:L/PR:N/UI:R). The impact is confined to the sandbox, so compromise of the host operating system would require chaining a separate sandbox-escape vulnerability. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google - the reporting party - has released a fixed build.
Remote code execution inside the Chrome renderer sandbox is possible on Chrome builds prior to 155.0.8059.39, where a use-after-free in the WebRTC component can be triggered by a crafted HTML page. The flaw is rated 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and assigned Chromium severity High; no authentication or prior privileges are required, but the victim must open or be redirected to the attacker's page (UI:R). Impact is confined to the renderer sandbox - reaching the host OS would require chaining a separate sandbox-escape vulnerability - and no public exploit was identified at time of analysis; the primary exposure window is the short period before Chrome's auto-update moves users to the fixed build.
Remote code execution inside the Chrome renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a use-after-free defect in the HTML handling path can be triggered by a crafted HTML page. Any user running an unpatched desktop Chrome who loads attacker-controlled web content (CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) can be targeted; no credentials or elevated privileges are required, but mandatory user interaction (UI:R) and the renderer sandbox confinement limit the direct blast radius, since escaping the sandbox to the host OS would require a separate, distinct vulnerability not covered by this CVE. Google has shipped a vendor patch (155.0.8059.39) and the issue was reported through the Chrome vulnerability program with a Chromium severity rating of High; no public exploit code and no confirmed active exploitation have been identified, and the affected-code flaw is consistent across the CPE wildcard for google:chrome.
Use-after-free in Google Chrome's Web Audio implementation affects versions prior to 155.0.8059.39, where a remote attacker can achieve arbitrary code execution inside the browser's renderer sandbox by getting a victim to open a crafted HTML page that exercises the Web Audio API. The flaw carries an assessed CVSS of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or non-default configuration is required, but the attack does depend on user interaction (loading the page) and the resulting code execution is confined to the renderer sandbox, so full host compromise would require chaining a separate sandbox escape. Chromium rates the issue High severity, the vendor has published a fix in 155.0.8059.39, and no public exploit code has been identified at time of analysis; there is no CISA KEV confirmation of active exploitation.
Remote code execution confined to Chrome's renderer sandbox is possible in Google Chrome prior to 155.0.8059.39, where a use-after-free in the browser's Bindings layer can be triggered when a victim opens a crafted HTML page. The attack is unauthenticated (PR:N) but depends on user interaction (UI:R), and because the assessed scope is unchanged (S:U), code execution is contained inside the renderer sandbox - reaching the host would require a separate sandbox-escape vulnerability. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Chrome's automatic update mechanism narrows the realistic exposure window, making this a high-priority patch item rather than an emergency.
Incorrect authorization in Google Chrome's FileSystem component allows a remote attacker to break out of the browser sandbox and potentially execute arbitrary code at the operating system level on desktop builds prior to 155.0.8059.39. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6), no authentication or prior privileges are required, but exploitation is not automatic: the attacker must use social engineering to convince the victim to open a crafted HTML page, which aligns with CISA's SSVC rating of "not automatable" and a technical impact of "total" given the scope change across the sandbox boundary. There is no CISA KEV listing and no public exploit code identified at time of analysis, and a vendor patch is available, so this should be treated as a high-severity, patch-now issue rather than an actively exploited emergency.
Out-of-sandbox code execution is achievable in Google Chrome desktop builds prior to 155.0.8059.39 by exploiting a use-after-free in the browser-process TabStrip component, reached when a victim is socially engineered into opening an attacker-crafted HTML page. The flaw carries a 9.6 CVSS (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) because the corrupted component sits outside the renderer sandbox, so a successful exploit escapes Chrome's primary containment boundary; however, it is not a zero-click bug and no public exploit identified at time of analysis, and CISA's SSVC assessment rates exploitation as 'none' with Automatable 'no'. A vendor-released patch (155.0.8059.39) is available, making this a high-priority but currently non-weaponized patch-now item rather than an active incident.
Remote code execution outside the browser sandbox in Google Chrome prior to 155.0.8059.39 allows a remote attacker to execute arbitrary code on a victim's system via a crafted HTML page. The flaw is a use-after-free in the browser's Core component, and exploitation requires the victim to open attacker-controlled web content (UI:R) while no authentication or special privileges are needed (PR:N); the CVSS score is 9.6 with scope change (S:C) reflecting sandbox escape. Despite the high impact, there are no exploitation signals: no public exploit identified at time of analysis and the SSVC assessment lists exploitation as none, though the total technical impact and wide deployment make timely patching a priority.
Use-after-free in Google Chrome's Storage component (all versions prior to 155.0.8059.39) allows a remote attacker to execute arbitrary code outside the sandbox, but only after the attacker has already compromised the renderer process - typically by chaining a separate renderer bug - and only when a victim loads a crafted HTML page (CVSS 8.3, AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H). Because a prior renderer compromise, user interaction, and non-trivial heap grooming are all required, this is a second-stage sandbox-escape primitive rather than standalone initial access. No public exploit code has been identified at time of analysis, CISA SSVC records exploitation as none, and Google has shipped a vendor patch in Chrome 155.0.8059.39.
Remote code execution inside the Chrome renderer sandbox is possible in Google Chrome versions prior to 155.0.8059.39 through a race condition in the V8 JavaScript engine, triggered when a victim loads a crafted HTML page. The flaw requires no authentication (PR:N) but does require user interaction (UI:R) and depends on winning a non-deterministic timing window, which is reflected in the assessed AC:H and makes reliable exploitation harder. Resulting code execution stays within the renderer sandbox, so escaping to the host OS would require chaining a separate sandbox-escape vulnerability; no public exploit code has been identified at time of analysis, and vendor patches are available.
Use-after-free in Google Chrome's parser allows remote attackers to execute arbitrary code within the browser's renderer sandbox by convincing a victim to visit a crafted HTML page. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires user interaction (UI:R) but no authentication (PR:N). The flaw carries a High Chromium severity rating (CVSS 8.8) and no public exploit has been identified at time of analysis; however, standalone impact is constrained because the description specifies code execution 'inside the sandbox,' meaning a second vulnerability would be needed to escape to the host.
A use-after-free in the Chrome Tabs component of Google Chrome on macOS allows a remote attacker to potentially execute arbitrary code outside the sandbox when a victim loads a crafted HTML page, affecting all builds prior to 155.0.8059.39. Exploitation is unauthenticated (CVSS PR:N) but requires user interaction (UI:R) - the victim must navigate to or open attacker-controlled web content, with no zero-click vector indicated, and reliable code execution additionally depends on successful heap grooming of the freed object. The issue is assessed as a genuine high-priority problem rather than a high-CVSS-but-low-real-risk case (CVSS 9.6, scope-changed), and no public exploit was identified at time of analysis; a vendor patch is available in Chrome 155.0.8059.39.
Use-after-free in Chrome's Tint shader compiler lets a remote attacker achieve code execution outside the browser sandbox when a victim opens a crafted HTML page - the page drives Chrome's WebGPU pipeline so that Tint compiles a malicious WGSL shader that triggers the memory-safety flaw. The flaw affects Google Chrome builds prior to 155.0.8059.39 and is rated 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), with the scope-change sub-score reflecting that successful exploitation escapes the renderer sandbox and yields host-level impact; no authentication is needed, but the attacker must convince the user to visit the page (UI:R). No public exploit code has been identified at time of analysis and CISA's SSVC assessment records no exploitation, so this is currently a high-priority patch-now issue rather than an actively exploited one; a vendor patch is available in the 155.0.8059.39 stable release.
Out-of-sandbox code execution in Google Chrome for iOS (versions prior to 155.0.8059.39) stems from a missing authorization check that lets a remote, unauthenticated attacker who socially engineers a victim into opening a crafted HTML page run arbitrary code outside the browser sandbox (CVSS 3.1 base 9.6, AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, CWE-862). Exploitation is not possible without user interaction - the victim must navigate to or open attacker-controlled content on a vulnerable iOS Chrome build - and no public exploit code was identified at time of analysis, with no KEV confirmation of active exploitation. The combination of a scope-changing sandbox escape with high confidentiality, integrity, and availability impact makes this a high-priority browser flaw, but the mandatory user interaction and the narrow affected population (only unpatched iOS Chrome builds) keep it short of an emergency-patch situation.
Use-after-free in the ANGLE graphics layer of Google Chrome allows a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page; the vulnerable code path is present in Chrome builds prior to 155.0.8059.39. Exploitation is not automatic - the attacker must lure the user into rendering the malicious page (UI:R), but no credentials are required and the assessed CVSS:3.1 vector scores 9.6 with a scope change (S:C) because successful exploitation escapes Chrome's primary containment boundary rather than staying inside the renderer sandbox. Only publicly available exploit code would normally elevate this beyond an urgent patch-now item: at the time of analysis there is no indication of confirmed active exploitation (no CISA KEV listing) and no public exploit identified, while a vendor patch is available. Note that the description scopes the flaw to Chrome on Android, whereas the only vendor reference is the Desktop stable-channel release notes - the affected platform should be verified against the vendor advisory before relying on a platform-specific assumption.
Sandbox escape in Google Chrome versions prior to 155.0.8059.39: a race condition (CWE-362) in the browser's font handling can be triggered when a victim renders a crafted HTML page, potentially allowing a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox. Exploitation requires the target to load or view the attacker-controlled page (UI:R) and depends on winning a timing-sensitive race (AC:H), which typically demands repeated attempts and precise memory grooming, making this a credible high-priority browser flaw rather than a confirmed emergency. No publicly available exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and a vendor patch is available from Google.
An integer overflow in the WebGL implementation of Google Chrome on Android lets a remote attacker potentially execute arbitrary code outside the browser sandbox on devices running any build prior to 155.0.8059.39. The CVSS 3.1 base score is 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), meaning exploitation is unauthenticated but requires the victim to open an attacker-controlled HTML page that exercises the vulnerable WebGL code path; the scope change (S:C) reflects the potential escape from Chrome's renderer sandbox rather than a mere renderer crash. At time of analysis there is no public exploit identified, CISA's SSVC assessment records Exploitation: none and Automatable: no, and a vendor patch exists, so the issue is high priority on impact and patch urgency rather than on observed exploitation. Because WebGL is enabled by default on Android Chrome, no special configuration is needed on the victim side beyond navigation to the malicious page.
Arbitrary code execution outside the browser sandbox is possible in Google Chrome on macOS prior to 155.0.8059.39, where a timing-dependent race condition (CWE-367) in the Core component can be won to break out of the renderer's sandbox. Exploitation is conditional rather than a single remote shot: the attacker must already have compromised the renderer process, must socially engineer the victim into opening and interacting with a crafted HTML page (UI:R), and must win a non-deterministic race that the AC:H rating and CISA's SSVC assessment (Exploitation: none, Automatable: no) indicate is unreliable and not readily scriptable. No public exploit code has been identified at time of analysis, and Google has shipped a fixed build, 155.0.8059.39; because the mandatory pre-existing renderer compromise is a high bar, this is best treated as a conditional priority to be handled through normal patching cadence rather than an emergency.
A race condition in Google Chrome's Fonts component prior to version 155.0.8059.39 lets a remote attacker escape the browser sandbox and execute arbitrary code at the browser's privilege level, but only after the attacker has already compromised a sandboxed renderer process through some separate, unrelated vulnerability. The exploit additionally requires the victim to load a crafted HTML page (UI:R) and the attacker to win a timing-dependent race (AC:H), so this is best understood as a sandbox-escape primitive rather than a standalone initial-access vector. There is no public exploit identified at time of analysis - CISA's SSVC assessment rates exploitation as 'none' and the flaw as not automatable - and a vendor-released patch (155.0.8059.39) is available, making this a high-priority defense-in-depth fix rather than a catastrophic unpatched bug.
Type confusion in ANGLE, Chrome's OpenGL ES abstraction layer, lets a remote attacker who has already compromised the renderer process execute arbitrary code outside the browser sandbox in Google Chrome versions prior to 155.0.8059.39. The victim must load attacker-controlled graphics content (crafted HTML invoking WebGL/ANGLE paths), so user interaction is required, and the bug cannot be triggered by merely visiting a page without a separate renderer exploit first - it is a second-stage sandbox-escape primitive in a multi-bug chain rather than an initial-access vector. No public exploit identified at time of analysis; CISA's SSVC assessment rates exploitation as none and automatable as no, but technical impact as total, consistent with the CVSS scope change (S:C), high confidentiality and integrity impact, and the High Chromium security severity rating.
Incorrect authorization (CWE-863) in Google Chrome's SiteIsolation component allows an unauthenticated remote attacker to execute arbitrary code in the browser when a victim loads a crafted HTML page, a flaw Google rates High and that carries a CVSS base score of 9.6. Exploitation is limited by the required user interaction (UI:R) - the victim must visit attacker-controlled or compromised web content on a build older than 155.0.8059.39 - so delivery hinges on drive-by browsing or social engineering rather than unattended compromise, consistent with CISA's SSVC rating of non-automatable. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in Chrome 155.0.8059.39.
Use-after-free in Google Chrome's Track component (versions prior to 155.0.8059.39) allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox when a victim loads a crafted HTML page. The flaw carries a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning it is network-reachable, low-complexity, and requires no authentication, with mandatory user interaction - the victim must navigate to or be redirected to attacker-controlled content - as the only gating prerequisite. Google rates the issue Critical and shipped a fix in the 155.0.8059.39 stable-channel release; no public exploit code has been identified at time of analysis, and the escape from the browser sandbox would require a separate, independent vulnerability.
Memory corruption in Google Chrome's Navigation component - a use-after-free (CWE-416) - allows a remote attacker to execute arbitrary code outside the browser sandbox on any Chrome installation prior to 155.0.8059.39 by getting a user to load a crafted HTML page. The flaw is rated Critical by Chromium with a CVSS 3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H): no authentication is required and delivery is network-based, but exploitation still depends on the victim rendering attacker-controlled content, and the scope change (S:C) reflects that successful exploitation escapes the renderer sandbox to affect the host system. No public exploit has been identified at time of analysis (CISA SSVC Exploitation: none, Automatable: no), and this is a genuine high-priority issue rather than an inflated high-CVSS score.
Use-after-free in the browser-process component of Google Chrome before 155.0.8059.39 lets a remote attacker execute arbitrary code outside the sandbox when a victim opens a crafted HTML page. Exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N) but requires the user to navigate to attacker-controlled content (UI:R); the scope change and high confidentiality, integrity, and availability ratings reflect that a successful page load escapes the renderer sandbox to reach host-level code execution, which pushes the base score to 9.6 and earns a Chromium security severity of Critical. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV, so the practical near-term risk comes from the low complexity of the trigger (phishing, malvertising, or a compromised site) rather than from observed attacks. Vendor-released patch: Chrome 155.0.8059.39.
Remote code execution outside the browser sandbox is possible in Google Chrome builds prior to 155.0.8059.39 through a use-after-free flaw in the built-in Chromecast (Cast) component: an attacker who gets a victim to render a crafted HTML page can corrupt freed memory and run arbitrary code with the browser's privileges (CVSS 9.6, Chromium severity Critical). The sole hard prerequisite is user interaction - no credentials or elevated privileges are required per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) - and because Cast ships with standard desktop Chrome rather than as an optional extension, the exposed population is essentially every unpatched Chrome installation. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google has released a fixed build.
A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an attacker within Bluetooth radio range execute arbitrary code on unpatched Android devices, with no user interaction and no additional execution privileges required. The flaw is rated CVSS 9.8 under the vendor's AV:N vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); our independent assessment re-scores it AV:A because exploitation realistically requires the device's Bluetooth to be enabled and the attacker to be within radio range to deliver crafted CCC/GATT traffic, while agreeing that no authentication or victim action limits the attack. No public exploit code and no confirmed in-the-wild exploitation have been identified at time of analysis, and a fix is published in the Android/Pixel security bulletin dated 2026-10-01.
Path traversal in Dell System Update (DSU) versions prior to 2.3.0.0 allows an unauthenticated remote attacker to escape the intended restricted directory when the DSU client processes crafted pathnames in update content, resulting in filesystem access. Because DSU operates with elevated privileges, exploited path traversal can escalate to arbitrary code execution as root, potentially compromising both the application and the underlying operating system. Exploitation is not automatic: the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) shows remote, unauthenticated reach but a mandatory user interaction step, and no public exploit code was identified at time of analysis. Dell has published a fixed release, and this is a genuinely high-priority flaw rather than merely a high-CVSS outlier.
Remote code execution in Payload CMS before 3.90.0 (and canary builds before 4.0.0-canary.34) lets a remote, unauthenticated attacker execute arbitrary code by sending a crafted request to the public first-register operation. The flaw only applies to instances that have local authentication enabled and have not yet had their first admin user created, i.e. a freshly deployed, re-provisioned, or ephemeral instance still inside its initial setup window; once an admin exists the attack surface disappears. No public exploit identified at time of analysis, and no evidence of active exploitation (not in CISA KEV), though the CVSS 8.1 score with full confidentiality, integrity and availability impact makes this a high-priority fix for anyone running uninitialized deployments.
Unauthorized read access to stored form submissions and form email configuration in Payload CMS deployments running the @payloadcms/plugin-form-builder plugin before 3.90.0 (and 4.0.0-canary versions before 4.0.0-canary.34) is achievable by an authenticated non-admin user, based on the vendor patch, which replaces a permissive 'any logged-in user' read rule with a check that the requester belongs to the configured admin user collection. The published CVE record characterizes the flaw as remote code execution (CWE-94, CVSS 10.0), but the actual shipped fix is an access-control tightening on the Forms and FormSubmissions collections plus tests asserting that users from unrelated collections are denied, so the verifiable impact is a confidentiality breach of form data rather than code execution; these conflicting signals should be reconciled with the vendor advisory before prioritization. There is no public exploit identified at time of analysis and no indication of confirmed active exploitation, but the authorization requirements (the CVSS vector claims unauthenticated, while the patch implies a logged-in non-admin account is needed) should be confirmed against the vendor before assuming unauthenticated exposure.
Unauthenticated remote code execution in the SPIP Crayons plugin before 3.5.0 allows any remote attacker to take over a SPIP site by reaching crayons_store.php without the secu_ anti-forgery parameter, which causes the authorization dispatcher to select an unconditionally-true handler instead of the legitimate modification check. With authorization bypassed, the attacker can write an arbitrary .html skeleton file, read configuration files that expose the site secret, and forge a signed AJAX context that executes the planted skeleton as PHP under the web-server user. The assessed impact is high across confidentiality, integrity, and availability (CVSS:3.1 AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H; vendor-scored 9.3), exploitation requires only that the Crayons plugin be installed and enabled below 3.5.0, and no public exploit code was identified at time of analysis though the flaw is trivially reachable and unauthenticated.
Prototype pollution in Payload CMS's @payloadcms/plugin-import-export module lets an unauthenticated remote attacker submit prototype-sensitive field paths to the plugin's endpoints, corrupting object prototypes and triggering unintended application behavior that can escalate to remote code execution. The flaw affects Payload 3.0.0 through versions before 3.88.0 and 4.0.0-canary.0 through versions before 4.0.0-canary.27, but only when the Import Export plugin is installed and enabled - sites without that plugin are unaffected. No public exploit code has been identified at time of analysis, and exploitation is gated by the presence of a reachable prototype-pollution gadget in the target application, so real-world impact is conditional even though the vendor advisory and a 9.3 CVSS 4.0 score (independent assessment: CVSS 3.1 8.1-range with AC:H) both flag it as high severity.
HortusFox versions before 6.2 expose an authenticated remote code execution path through the theme import feature (ThemeModule::startImport): an uploaded ZIP archive is extracted into the public web root before file names, extensions, or content are validated, so an attacker with an administrator account can bundle a PHP payload and an .htaccess file that re-enables PHP execution and then execute arbitrary OS commands as the web-server user by requesting the dropped file under the themes directory. Exploitation is gated by administrator privileges (CVSS PR:H), so practical risk depends on obtaining or compromising an admin account; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV). The vendor addressed the flaw in the 6.2 release, and the issue is tracked under CWE-434 (unrestricted upload of a file with a dangerous type).
Openapi-python-client before 0.29.1 fails to neutralize attacker-influenced content from an OpenAPI document when rendering string, docstring, and f-string contexts, so a malicious or untrusted specification can cause arbitrary Python to be emitted into the generated client - code that then executes when that client is imported, compromising the integrity of the importing environment and potentially its confidentiality and availability. Exposure is conditional: it requires someone to generate a client from a spec they do not fully control (a third-party, public, or otherwise untrusted API definition) and then import the generated code, which is the trigger point, so organizations generating only from trusted internal specs are effectively unaffected. The flaw is rated 8.4 under CVSS 4.0 in the source data (independent assessment maps it to CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), which is consistent with a serious but conditionally triggered supply-chain and code-generation issue rather than a remotely reachable mass-exploitation vector. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has shipped a fix in version 0.29.1.
Code injection in Microsoft Kiota 0.5.0 through pre-1.35.0 allows attacker-controlled text embedded in an OpenAPI description to break out of the generated Java or PHP documentation comment and execute in the consuming application or build environment once that generated source is compiled and loaded (Java) or loaded (PHP). The flaw is reachable unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction: a developer or CI pipeline must generate client code from an untrusted or tampered spec and then build or load the output, making this a build-time/supply-chain path rather than an attack on already-deployed runtime services. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV; CVSS 3.1 base score is 8.8, and the issue is fixed in 1.35.0.
Heap buffer overflow in libmikmod's Oktalyzer (.okt) loader lets a crafted module corrupt heap memory and potentially achieve code execution, because a 16-bit track-count field (numtrk = numpat * numchn) can be made to wrap while pattern data is still written for the full, unwrapped track count. Any application linked against libmikmod before 3.3.14 is affected, and exploitation requires the victim to open or otherwise process an attacker-supplied .okt file, matching the independently assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R (7.8) rather than a remotely reachable condition. No public exploit identified at time of analysis, and the 3.3.14 release rejects overflowing track counts outright.
Heap buffer overflow in libmikmod before 3.3.14 is triggered when an application linked against the library parses a crafted DSM module whose numchn and numpat header fields produce a product that overflows the 16-bit UWORD truncation in DSM_Load(), corrupting heap memory and potentially enabling code execution. The issue is local and file-based: an attacker must deliver a malicious DSM file and a victim must open or play it, so it is not a drive-by remote threat; no authentication or special privileges are required, and no public exploit has been identified at time of analysis. A vendor-released patch is available in libmikmod 3.3.14.
PHP code injection in the Smarty templating engine allows remote code execution in applications running Smarty 4.x before 4.5.8 or 5.x before 5.8.5 that render templates through the extends:/multi-component inheritance path with caching enabled. When such a template is compiled, the top-level unifunc never restores its nocache_hash, so the value is null; combined with an empty regex alternative in the cache-split logic, attacker-controlled assigned data containing a forged /*%%SmartyNocache:%%*/ marker is copied verbatim (bypassing PHP-tag neutralization) into the regenerated PHP cache file and executed on the next include. Exploitation is unauthenticated per the vendor CVSS vector (PR:N) but is gated by strict preconditions - inheritance-path templates, active caching, unescaped attacker-controlled output, and a fresh PHP process that reloads the compiled file after the cache entry is evicted (TTL expiry or cache clear) while compiled files persist - making it conditional rather than reliably on-demand; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis.
Insecure deserialization in the TrueLayer Magento 2 Plugin's Psr16CacheAdapter component allows an attacker who already has write access to the Magento cache backend (Redis or Memcached) to achieve arbitrary code execution via crafted PHP objects. The flaw arises from PHP's unserialize() being called without class restrictions, and exploitation requires both cache-write capability-obtainable through local filesystem access or an exposed cache service-and the presence of a usable gadget chain in the deployed Magento/Adobe Commerce environment. Although rated CVSS 7.5, real-world risk is materially lower because the attack preconditions are stringent; no public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited.
Authenticated remote code execution in Craft CMS 5.10.13.2 allows any low-privilege Control Panel user to run operating-system commands as the PHP/web-server process by injecting Twig through the app/render-components action. The attack requires only basic CP access; a non-admin Team user with no optional permissions was shown to override an EntryType uiLabelFormat and trigger an Entry render that evaluates attacker-controlled Twig via renderObjectTemplate(). No public exploit identified at time of analysis, but the impact is severe because the render path is unsandboxed and can reach PHP functions such as system().
Remote code execution (RCE) in WPShopmart Tabs Responsive plugin for WordPress (versions <= 2.5) allows an authenticated attacker with Editor-level privileges to execute arbitrary code on the server. This high-severity vulnerability (CVSS 8.0, CWE-94) requires high-complexity conditions (AC:H) and no user interaction (UI:N). No public exploit code has been identified at time of analysis; risk is concentrated on multi-user sites where untrusted users have elevated editing roles.
Remote code execution in WooCommerce Designer Pro (versions up to 1.9.33) allows authenticated attackers with Subscriber-level access or higher to execute arbitrary code on the server. The flaw is a code injection (CWE-94) with a CVSS score of 9.9 (Critical), requiring no user interaction and resulting in complete loss of confidentiality, integrity, and availability (scope change). Exploitation is most realistic on WooCommerce storefronts that permit open customer self-registration; no public exploit identified at time of analysis. The independent assessment confirms this is a genuine high-priority issue rather than a theoretical risk.
Remote code execution in the ACPT (Premium) WordPress plugin affects all versions up to and including 2.0.66, allowing an authenticated attacker with only subscriber-level access to run arbitrary code on the server. The chain works by abusing a REST API form-creation endpoint that performs no capability check, planting a malicious email_settings payload, and then triggering a form submission so the plugin's unsandboxed Twig environment renders attacker-controlled template expressions during email generation. No user interaction is required and no public exploit code has been identified at time of analysis, though the low authentication bar (subscriber) makes it considerably more dangerous on sites with open registration; exploitation is not confirmed actively exploited (no CISA KEV listing), and the vendor changelog points to a fixed release.
Remote code execution in Immich before 3.2.4 lets any authenticated non-admin user with upload permission run arbitrary code inside the immich-server container. The exploit chains two crafted SVG assets: a stored reference asset and a second 'delayed-marker' SVG whose attacker-controlled <image href> value reaches ImageMagick's unrestricted MSL and VIDEO coders after the file bypasses libvips' native SVG loader, with execution occurring when the server generates a thumbnail. The attack is high-complexity and depends on the ImageMagick fallback path being reachable with those coders enabled; version 3.2.4 contains the fix, and no public exploit code was identified at time of analysis.
Unauthorized code execution during the boot process is possible on AMD Zynq UltraScale+ MPSoC, Zynq UltraScale+ RFSoC, and Kria SOM devices when an attacker with physical or local USB access can drive oversized Device Firmware Upgrade (DFU) download requests while the device is held in USB boot mode. The flaw is an out-of-bounds write (CWE-787) in the USB boot-mode DFU path: missing boundary validation allows the download to overflow the DDR receive buffer and corrupt adjacent First Stage Boot Loader (FSBL) memory before the FSBL hands off to later boot stages. AMD rates this 7.5 (CVSS 4.0 AV:L/AC:L/AT:P/PR:N/UI:N with High confidentiality, integrity, and availability impact to the device); no public exploit code and no confirmed active exploitation were identified at time of analysis, and practical exposure is limited to devices whose boot configuration actually permits USB boot rather than QSPI/eMMC/SD.
Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.
Authenticated users of Langflow versions prior to 1.9.0 can achieve remote code execution on the underlying host by adding an MCP server that uses the Stdio transport, because the user-supplied command field is passed directly to a shell with no validation, allowlisting, or sandboxing; the injected command executes immediately when the MCP server list is fetched, requiring no further victim interaction, and the env field additionally permits environment-variable injection (for example LD_PRELOAD or PATH overrides) for a second code-execution path. The vendor has issued a fix in 1.9.0 that restricts MCP stdio commands to an allowlist and blocks dangerous environment variables, and no public exploit code has been identified at time of analysis. The 9.9 CVSS score reflects the vector's scope change (S:C) and high confidentiality, integrity, and availability impact, though practical exploitability depends on the attacker holding a valid authenticated Langflow account with access to MCP server configuration.
Code execution in Newell Brands DYMO ID 1.5.1.71 occurs because the application resolves its plugin Modules directory relative to the process working directory, letting an attacker who places a malicious plugin module or DLL alongside a crafted job file load arbitrary code at the victim's privilege level once that job file is opened. The issue is local and file-delivery based rather than network-reachable, requires explicit victim interaction (opening the crafted job), and grants only the privileges the victim already holds, so it cannot self-propagate; no public exploit code and no CISA KEV entry were identified at time of analysis. The vendor has released a fix in DYMO ID 1.6.0.
Authenticated Ghost Administrators on versions 6.10.3 through 6.63.x can achieve remote code execution by installing a crafted theme that abuses how Ghost resolves theme translation (i18n) files, allowing path traversal into attacker-controlled code. Exploitation requires a high-privilege Administrator account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) and no victim interaction beyond the attacker's own admin actions; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Because the attacker population is limited to trusted or already-compromised admin accounts rather than anonymous remote users, this is a high-severity but access-gated issue rather than a mass-exploitation priority.
Remote code execution in Ghost CMS 6.56.0 through 6.66.x lets any authenticated staff user - including the lowest-privilege Contributor role - execute arbitrary commands on the Ghost server by creating a bookmark card that points to an attacker-controlled website serving a crafted SVG. The root cause is a code-injection flaw (CWE-94) in the SVG handling path of an image-processing library bundled with Ghost, and successful exploitation yields full confidentiality, integrity, and availability impact on the host. Exploitation requires a valid Ghost staff login (the vendor vector claims PR:N, but our assessed vector of PR:L/UI:N is the accurate prerequisite), and there is no public exploit identified at time of analysis. Ghost 6.67.0 is the fixed release.
Code execution via local privilege escalation is possible in Google Android's Bluetooth AVRCP handling (handle_app_val_response in btif_rc.cc) because of a race condition (CWE-362) that can corrupt shared state in the Bluetooth stack. The flaw is rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N) and affects Android 16, Android 16-qpr2, and Android 17; an attacker must already have a low-privilege app installed on the device and must repeatedly drive the AVRCP remote-control code path to win a narrow timing window, with no user interaction required. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, so while the technical impact is total if the race is won, the high attack complexity and local-only prerequisites keep this a lower-urgency item than a remotely reachable, deterministic bug.
Heap-based out-of-bounds write in Android's Bluetooth stack, specifically the cfg2prop routine in btif_storage.cc, can be triggered when the Bluetooth subsystem converts attacker-influenced bonded/stored device configuration data into Bluetooth properties, potentially leading to remote code execution. Affected builds are Android 16, Android 16-qpr2, and Android 17; the assessed vector requires low privileges (PR:L, consistent with a pairing/component-level context) and no user interaction, and real-world reachability is expected to be radio-adjacent (a nearby, paired, or spoofed Bluetooth device) rather than arbitrary internet access, even though the vendor-assigned vector carries AV:N. No public exploit code has been identified and SSVC records exploitation as none at time of analysis, but the flaw is memory-corruption class with total technical impact, so it warrants priority patching on devices where Bluetooth is enabled and pairing is common.