Remote code execution in Atlantis (runatlantis/atlantis) 0.4.0 through 0.47.0 lets an authenticated contributor whose pull request is eligible for an Atlantis plan inject shell metacharacters through the PR-controlled Terraform workspace value in atlantis.yaml, executing arbitrary commands as the Atlantis service account. The flaw requires no custom workflows, no allow_custom_workflows, no apply permission and no malicious Terraform provider; fork-based contributors reach it only when --allow-fork-prs is enabled, while eligible same-repository branches need no such flag. Because injected commands inherit the Atlantis process environment, exfiltration of cloud-provider, Terraform and VCS credentials plus access to state, plan files, checkouts and the server's network identity are all in scope; exploitation is limited to authenticated contributors (PR:L), public PoCs demonstrating the workspace payload exist, no public working exploit code is confirmed, and vendor-released patch 0.47.1 resolves the issue.
A regular-expression denial of service exists in the Datadog APM client for Node.js (dd-trace-js) versions 2.0.0 through 5.131.0 and 6.0.0 through 6.20.0, where the default DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP can backtrack excessively on attacker-controlled URL query strings. Because the pattern runs synchronously while recording HTTP URL span metadata - and is enabled by default for affected HTTP tracing integrations that capture query strings - an unauthenticated remote attacker who can reach an instrumented endpoint and supply a crafted query string can pin the CPU and stall request processing, degrading or taking down the instrumented application. Impact is confined to availability with no data exposure; no public exploit has been identified at time of analysis, and vendor fixes ship in dd-trace 5.131.1 and 6.20.1.
Symlink-following read paths in FileBrowser Quantum serve files from outside a user's assigned scope: download, preview, media/subtitle, OnlyOffice and public-share handlers resolve links with filepath.EvalSymlinks and then open the resolved target without checking that it is still inside the source root. The unauthenticated worst case, reflected in the CVSS vector (PR:N, S:C, C:H), is a holder of a public share link reading any file the server process can reach through a symlink reachable in the shared directory; an authenticated user with download access achieves the same, including cross-tenant reads where scopes overlap. Exposure requires that a qualifying symlink already exists in the served tree - common with bind-mounted host directories in Docker deployments - and affects filebrowser versions before 1.5.2-stable and 2.0.0-beta through 2.0.1-beta, which are fixed by 1.5.2-stable and 2.0.1-beta. A public proof-of-concept walkthrough accompanies the GHSA advisory and was demonstrated live against 1.3.3-stable; there is no CISA KEV entry, so active exploitation is not confirmed.
Stored cross-site scripting in the TinyMCE rich text editor's media plugin lets a low-privileged authenticated content author plant a crafted span carrying data-mce-object and data-mce-p-<event> handler attributes that the editor materialises into real video/audio/img elements and executes before sanitisation runs. Affected are TinyMCE 7.9.3 and versions 8.5.1 through 8.9.2 with the media plugin enabled; the vendor fixed it in 7.9.4 and 8.9.3 by building those elements in a non-scripting document. Exploitation needs authenticated content-injection access plus a second user processing the stored content, so this is a genuine but conditional priority rather than a top-tier emergency; no public exploit was identified at the time of analysis and there is no CISA KEV entry.
Cross-site scripting in the CKEditor 5 engine package allows crafted editor content - specifically incoming `style` attribute values - to reach a prototype-pollution path in the bundled `es-toolkit` library and result in unauthorized JavaScript execution in the browser. Affected are CKEditor 5 releases from 45.0.0 up to but excluding 47.7.4 on the LTS branch, and from 48.0.0 up to but excluding 48.5.1 on the current branch; per the CVSS vector (AV:N/AC:L/PR:L/UI:N) the actor needs a low-privilege foothold, i.e. the ability to feed content into the editor, rather than a fully anonymous request, and no user interaction beyond the editor processing that content. Vendor patches are available in 47.7.4 and 48.5.1, and no public exploit was identified at time of analysis; this is a patch-now-grade priority within its deployment scope rather than a drop-everything emergency.
Arbitrary file read in MLflow 3.10.0 through 3.16.1 allows remote attackers to store a server-local path as a prompt model version's artifact location and then retrieve files through the /api/2.0/mlflow/model-versions/get-artifact endpoint. Default mlflow server deployments are unauthenticated (CVSS PR:N), while basic-auth deployments are exposed to any authenticated user whose RBAC permits creating registered models. A public PoC reference exists but is not verified as working exploit code, and the vendor fix is available in 3.17.0; assessed priority is this_week.
High-severity integer overflow in EPICS Base 7.0.10 and earlier can be reached over the network without authentication or user interaction when a crafted EPICS protocol message carries a length value that is not properly validated. The resulting out-of-bounds memory write can destabilize or crash the affected process, producing denial of service; no public exploit has been identified at time of analysis, and CISA KEV does not list this CVE.
Out-of-bounds read in EPICS Base 7.0.10 and earlier lets a remote, unauthenticated attacker who can deliver a crafted message to an EPICS network service (Channel Access or PV Access) make the process read past the end of an allocated buffer, primarily crashing the service and potentially exposing adjacent memory. Affected deployments are typically control-system middleware on segmented or air-gapped facility networks, so real-world reachability depends on whether the protocol port is exposed to the attacker; default builds of all versions up to and including 7.0.10 are in scope. No public exploit was identified at time of analysis, and the vendor/coordinator advisory is ICSA-26-300-01; priority is this_week rather than emergency response.
Out-of-bounds read in EPICS Base 7.0.10 and prior allows unauthenticated remote attackers to crash or degrade an affected IOC/server and potentially disclose adjacent memory contents by sending a crafted network message with insufficiently validated element or length values. The issue is rated high availability impact with limited confidentiality exposure, and no public exploit was identified at time of analysis. Exploitation depends on reaching an EPICS Base service across the network, which in typical deployments sits on segmented control or OT networks.
Authenticated OS command injection in Sunhillo SureLine before 9.1.5 allows any holder of a web account to execute arbitrary commands as root on the appliance through the networkDiag.cgi diagnostic endpoint. The flaw affects SureLine 8.6.0 through versions before 9.1.5 and is triggered by URL-encoded newline (%0a) or ampersand (%26) separators in the ipAddr or dnsAddr parameters, bypassing the incomplete denylist from the CVE-2021-36380 fix. A vendor patch is available in 9.1.5, and no public exploit identified at time of analysis or CISA KEV entry was reported; the authentication prerequisite is the main barrier, though any web account suffices.
Unauthenticated remote file read in Sunhillo SureLine before 9.1.5 exposes sensitive system files, including /etc/shadow, the web user database, the root SSH private key, and the device TLS private key. The radarUpdater.cgi endpoint lacks authentication checks and does not sufficiently sanitize the filename parameter, allowing directory traversal sequences to read arbitrary files with root privileges. SureLine versions 8.0.0 up to but not including 9.1.5 are affected; a vendor patch is available, and no public exploit was identified at time of analysis.
An out-of-bounds write in the screen-image decoder of TeamViewer Full Client for Linux and macOS allows a remote attacker to execute arbitrary code on the victim's machine when the victim takes a user-driven action. Every build below 15.83 is affected, including the older branches prior to 13.2.154007 (macOS) / 13.2.154008 (Linux) and prior to 14.7.48868; the two described paths are opening a crafted .tvs session recording supplied by the attacker or participating in a remote-control session into which crafted screen-image data is injected, which is why the assessed vector carries UI:R with PR:N at CVSS 8.8. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the issue is prioritized for remediation this week given the code-execution impact on unpatched endpoints.
Privilege escalation in Cronicle through 0.9.120 lets an authenticated non-administrator user, or a scoped API key, that holds only create_events and run_events privileges inject top-level uid and gid fields into an event, which the root daemon then honours when launching the child process - so the low-privileged principal can run jobs as any local account, including root. Root compromise depends on the deployment mode: the advisory states a root-running daemon is the default per docs/Setup.md, while on a non-root daemon the impact is bounded by the daemon's own privileges; the injected identity also only survives with plugins that do not define their own uid, which is true of the shipped shellplug and urlplug defaults. This is a distinct sibling of the previously patched job-output injection tracked as CVE-2026-39401. Vendor-released patch: 0.9.121; no CISA KEV listing and no confirmed weaponized exploit, though the advisory publishes a working reproduction script; the assessed priority is to remediate this week.
Command injection in Ubiquiti airMAX M devices running firmware below 6.3.26 is reachable through a cross-site request forgery weakness in the device's web management interface, letting an attacker who lures a logged-in administrator to a malicious page run commands on the device with high confidentiality and integrity impact. 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 attacker needs no credentials of their own, but exploitation depends on a victim holding an active authenticated management session while loading the attacker-controlled page. No CISA KEV listing and no public exploit were identified at time of analysis, and EPSS is low at 0.38% (32nd percentile), making this a genuine priority for this week rather than a drop-everything emergency.
Command injection in the Autodesk Fusion Post Processor Utility extension (5.0.1 up to, but not including, 5.0.2) allows a remote attacker to execute arbitrary commands in the context of the current user when a victim opens a maliciously crafted .stack.json file. The attacker needs no credentials and the complexity is low, but exploitation is gated by user interaction: the hostile file must be delivered to and loaded by the target, so there is no zero-click remote path. No public exploit has been identified at time of analysis and the flaw is not in CISA KEV; impact is bounded by the privileges of the user who opens the file.
Privilege escalation in the Kirki plugin for WordPress (all versions up to and including 6.2.5) allows authenticated users with only Subscriber-level access to reach a vulnerable deserialization path in the 'get-single-symbol' branch of the kirki_post_apis() AJAX dispatcher, which lacks a capability check, and to inject a PHP object. Because a POP chain is present in the running code, a successful injection can overwrite an administrator's password and hand the attacker full administrative control of the site. The CVSS vector confirms network reachability, low privileges (PR:L), and no user interaction (UI:N) for a high-integrity, high-availability impact; EPSS is low at 0.30% (23rd percentile) and there is no KEV listing, so there is no public exploit identified at time of analysis, though the practical exposure is governed by whether a site permits open user registration.
Integer overflow in TeamViewer's remote-control screen processing component affects Full Client, Portable, and Remote Control App versions before 15.83, allowing a malicious or already compromised remote host to crash the viewer and, on some platforms, potentially execute code with the viewer process's privileges. The victim must deliberately establish an outbound remote-control session as the viewer (UI:R), so the attack model is targeted or social-engineering oriented rather than unsolicited remote compromise. No public exploit code has been identified at time of analysis, and vendor patches are available.
Memory corruption in the V8 JavaScript engine of Google Chrome before 156.0.8078.73 allows a remote, unauthenticated attacker to potentially execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. User interaction is mandatory and the resulting code execution is sandbox-contained, so compromising the host would require an additional sandbox-escape flaw; the CVSS 3.1 score is 8.8 with C:H/I:H/A:H. No public exploit was identified at time of analysis, and the vendor has released Chrome 156.0.8078.73; the priority is this week, not an emergency.
Loading a crafted HTML page can trigger memory corruption in Google Chrome's WebAudio component before version 156.0.8078.73, potentially allowing code execution inside the renderer sandbox. The attack is remote and requires no authentication, but user interaction is required because the victim must visit the attacker-controlled page; scope is unchanged, so host compromise would require chaining a separate sandbox escape. No public exploit was identified at time of analysis, and Google has released Chrome 156.0.8078.73 as the fix.
Use-after-free in Google Chrome's FileSystem component allows a remote attacker who convinces a victim to open a crafted HTML page to corrupt memory and potentially execute arbitrary code inside the browser's renderer sandbox in versions prior to 156.0.8078.73. Exploitation is network-reachable, low-complexity and requires no authentication, but it is gated by user interaction - the target must actively load and render the attacker-controlled page - and any resulting code execution is confined to the sandbox, so full host compromise would additionally require a separate sandbox escape. Google rates the issue Chromium security severity High and has released 156.0.8078.73 as the fixed build; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a patch-this-week item rather than a confirmed active campaign.
Improper input validation in the ANGLE graphics translation layer of Google Chrome on macOS prior to 156.0.8078.73 allows a remote attacker to potentially execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) reflects a low-complexity, network-reachable flaw that needs no privileges but requires the user to visit an attacker-controlled or compromised page; the impact is confined to the sandbox, so host compromise would require chaining a separate sandbox escape. No public exploit code or confirmed active exploitation was identified at time of analysis, and Google rates the issue as High severity with a vendor patch available in Chrome 156.0.8078.73.
Privilege escalation in the Supermicro BMC IPMI implementation allows an attacker who already holds a low-privilege BMC account to send crafted RAKP+ authentication messages and gain administrator-level access on affected MBD-X12SPI systems running firmware 01.07.20. The issue is rated CVSS 8.8 because exploitation is network-reachable, requires low privileges, and yields high confidentiality, integrity, and availability impact, although EPSS is low at 0.26% (17th percentile). No public exploit identified at time of analysis; reachability is limited to BMC management interfaces, typically IPMI/RMCP+ on UDP 623.
Improper input validation in the Skia graphics component of Google Chrome allows a remote, unauthenticated attacker to potentially achieve arbitrary code execution inside the browser sandbox by convincing a victim to load a crafted HTML page. All Chrome builds prior to 156.0.8078.73 are affected; the flaw is rated Critical by Chromium and carries a CVSS score of 8.8 with a user-interaction requirement (UI:R) and no privileges required (PR:N). Vendor-released patch: 156.0.8078.73, available from the Chrome stable channel advisory; the vendor describes the vulnerability as potentially allowing arbitrary code execution inside the sandbox, and no public exploit code has been identified in the provided sources, though the reference links to the Chromium issue tracker (restricted bug) and the stable-channel release notes.
Use-after-free in Google Chrome's Layout component allows remote attackers to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in versions before 156.0.8078.73. Exploitation requires user interaction but no authentication or special browser configuration; code execution is scoped to the renderer, and full host compromise would require chaining a separate sandbox escape. Vendor patch 156.0.8078.73 is available, no public exploit was identified at time of analysis, and the issue is rated high priority for this week rather than an emergency.
Improper input validation in Chrome's FileAPI component allows a remote, unauthenticated attacker to achieve code execution inside the renderer sandbox by convincing a victim to load a crafted HTML page; the flaw is fixed in Chrome 156.0.8078.73. Because the attacker must lure the user into opening the page (UI:R), delivery depends on a drive-by or social-engineering vector, and the resulting code execution is confined to the sandbox (S:U), so full host compromise would require chaining a separate sandbox escape. Google rates the issue Critical; no public exploit code is identified in the available data, and the fix is available from the vendor with a this-week remediation priority.
Use-after-free in Google Chrome's Paint component allows a remote attacker who persuades a user to load a crafted HTML page to potentially execute arbitrary code inside the browser sandbox on versions prior to 156.0.8078.73. The issue requires user interaction and does not by itself provide a sandbox escape, so full host compromise would require an additional vulnerability. No public exploit has been identified at time of analysis, EPSS is 0.24%, and a vendor patch is available.
A use-after-free (CWE-416) in Chromium's Animation component affects Google Chrome builds prior to 156.0.8078.73; a remote attacker who convinces a victim to load a crafted HTML page can trigger the memory-corruption condition and execute arbitrary code inside the browser sandbox. The CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting high confidentiality and integrity impact but requiring user interaction and remaining confined to the renderer sandbox until a separate sandbox escape is chained. There is no CISA KEV listing and no confirmed public exploit code in the supplied intelligence; a Chromium issue tracker reference exists but is not verified as working exploit code, and Google rates the flaw High with a vendor patch already released.
Improper input validation in the Headless component of Google Chrome before 156.0.8078.73 lets a remote, unauthenticated attacker who convinces a victim to load a crafted HTML page run arbitrary code inside the browser sandbox. The realistic exposure is less ordinary desktop browsing and more automated Headless Chrome deployments - CI pipelines, server-side rendering, scraping and PDF generation - that render attacker-influenced HTML. No public exploit code or active exploitation is confirmed in the available data; the vendor has released Chrome 156.0.8078.73 as the fix, and this is assessed as a genuine but moderate-urgency priority rather than an emergency.
WebRTC input validation in Google Chrome prior to 156.0.8078.73 can allow a remote attacker to potentially execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R, so no authentication is required but user interaction is necessary. No public exploit was identified at time of analysis, and a vendor patch is available in Chrome 156.0.8078.73.
Memory corruption in Google Chrome's Media component can let a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page, affecting Chrome releases prior to 156.0.8078.73. Exploitation requires user interaction and, with scope unchanged, is limited to renderer-process compromise rather than full host takeover unless combined with a separate sandbox escape. No public exploit identified at time of analysis; the vendor has released a fixed build, and this is a high-priority patch item rather than a drop-everything emergency.
Memory corruption in Google Chrome's V8 engine prior to 156.0.8078.73 can let a remote attacker who gets a user to load a crafted HTML page run arbitrary code inside the browser sandbox. The issue is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R) and requires user interaction; code execution is contained within the renderer sandbox, so full host compromise would require chaining a separate sandbox-escape flaw. No public exploit identified at time of analysis, and the vendor has released a fixed Chrome build, consistent with a this_week priority.
Memory corruption in Chrome's HTML handling lets a remote attacker potentially execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in Google Chrome desktop builds prior to 156.0.8078.73. The CVSS vector shows unauthenticated network delivery (PR:N, AV:N) but requires the user to navigate to the attacker's page (UI:R), and the description scopes any code execution to the sandbox (S:U), so full host compromise would need a separate sandbox escape. No public exploit code or in-the-wild exploitation has been identified at time of analysis, and Google rates the issue Chromium security severity High with a vendor fix already published in 156.0.8078.73.
Improper input validation in the UI layer of Google Chrome for Android before 156.0.8078.73 allows remote attackers to achieve code execution inside the browser sandbox when a victim loads a crafted HTML page. The attack requires user interaction (UI:R) but no authentication (PR:N), and impact is contained to the sandbox rather than the underlying Android OS, so full device compromise would need a separate sandbox-escape flaw. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS is low (0.22%, 13th percentile); Google rates the issue High severity and has released a patched build.
Use-after-free in Chrome's Video component lets a remote attacker execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in Chrome builds prior to 156.0.8078.73. Google rates the flaw High and our assessment matches CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H): no authentication is required, but the attacker depends on the user visiting or being redirected to attacker-controlled content, and the resulting code execution is confined to the sandbox (S:U), so host compromise additionally requires a separate sandbox escape. Signals conflict in a way worth stating plainly: the severity is high and the vuln.today priority label is this_week, yet EPSS is only 0.22% (13th percentile), there is no CISA KEV listing, and no public exploit was identified at time of analysis.
Memory corruption in the Media component of Google Chrome prior to 156.0.8078.73 lets a remote attacker who convinces a user to open a crafted HTML page potentially execute arbitrary code inside the browser sandbox. The flaw carries a CVSS score of 8.8 (AV:N/AC:L/PR:N/UI:R) and is rated High by Chromium security severity; exploitation is not confirmed in the wild, no public exploit code has been identified at time of analysis, and EPSS is low at 0.22% (13th percentile), though the vendor classifies it among the higher-severity fixes in this stable-channel release. Because the described impact is code execution inside the sandbox, host compromise would additionally require a separate sandbox-escape vulnerability not covered by this CVE; patched builds are available in 156.0.8078.73 and later.
Google Chrome desktop builds prior to 156.0.8078.73 mishandle input validation during SVG processing, allowing a remote attacker to achieve arbitrary code execution inside the renderer sandbox when a victim loads a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) reflects a high-severity flaw that requires user interaction and yields code execution confined to the sandbox, so full host compromise would additionally require chaining a separate sandbox-escape bug. No public exploit code has been identified at time of analysis, the EPSS score is low at 0.22% (13th percentile), and the issue is not in CISA KEV; the vendor has released a fix and priority is rated as remediation this week.
Heap-based buffer overflow (CWE-122) in Ubiquiti airMAX M, LTU PTMP, LTU PTP and SolarPoint/SolarSwitch firmware lets an attacker who is already on the adjacent network (CVSS AV:A) execute arbitrary code on the device with no authentication and no user interaction (CVSS 3.1 base 8.8, PR:N/UI:N), giving full confidentiality, integrity and availability impact. The adjacency requirement, not any account or feature prerequisite, is the limiting factor: default deployments of unpatched versions are exposed once the attacker shares the wireless link or local L2 segment. Fixed firmware is available from the vendor (airMAX M 6.3.26, LTU PTMP 2.4.2, LTU PTP 1.5.7, SolarPoint/SolarSwitch 2.0.3); there is no CISA KEV listing and no public exploit was identified at time of analysis, and EPSS is low (0.21%, 12th percentile), which places this at a this_week rather than emergency priority.
Use-after-free in Google Chrome's WTF component before 156.0.8078.73 allows a remote, unauthenticated attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page, with CVSS 3.1 scored 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Impact stays confined to the sandbox unless chained with a separate sandbox escape, and the precise trigger is not described in the supplied sources. Vendor-released patch: 156.0.8078.73; no public exploit was identified at time of analysis, and this is assessed as a genuine high-priority issue for this week rather than an emergency.
Remote code execution inside the Chrome renderer sandbox is possible in Google Chrome desktop builds prior to 156.0.8078.73, where improper input validation in the bundled Skia graphics library can be triggered by a crafted HTML page. The flaw is network-reachable and needs no privileges (PR:N), but it does require the victim to load attacker-controlled content (UI:R), and because CVSS scope is Unchanged it does not by itself escape the sandbox-full host compromise would require chaining a separate sandbox-escape bug. Google has shipped a stable-channel fix in 156.0.8078.73, and no public exploit code was identified at time of analysis.
Use-after-free in Chrome's Paint rendering component allows a remote, unauthenticated attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in any Chrome build prior to 156.0.8078.73. The user-interaction requirement (UI:R, opening the page) is the main limiting factor; no credentials or non-default configuration are needed since Paint is core browser functionality, yet successful exploitation yields code execution only within the renderer sandbox, so full system compromise would additionally require a separate sandbox-escape flaw. Google rates the issue Chromium security severity High and has released a fixed build; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vulnerability is prioritized for remediation this week.
Memory corruption in Google Chrome's Cache component before 156.0.8078.73 allows a remote attacker to execute arbitrary code inside the renderer sandbox by convincing a user to load a crafted HTML page. The flaw carries a CVSS score of 8.8 (AV:N/AC:L/PR:N/UI:R) and requires user interaction, which is the primary limiting factor; no public exploit code was identified at time of analysis. Google has released a patched build, and the issue is prioritized for remediation this week.
Memory corruption in the Skia graphics library shipped in Google Chrome before 156.0.8078.73 allows a remote attacker to achieve code execution inside the renderer sandbox when a victim loads a crafted HTML page. Affected users are those running Chrome builds prior to 156.0.8078.73; exploitation requires user interaction (CVSS UI:R, PR:N, AV:N), and the impact is confined to the renderer sandbox rather than host-level compromise. No public exploit is identified at time of analysis, and EPSS/KEV signals were not provided; the vendor classifies the issue as Chromium security severity High.
Use-after-free in the Turbolev component of Google Chrome allows an unauthenticated remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in builds prior to 156.0.8078.73. The CVSS score is 8.8, but exploitation requires user interaction and the impact remains sandbox-contained, so full host compromise would require chaining an additional sandbox-escape flaw. No public exploit code or active exploitation has been identified at time of analysis; Google has released a fixed build, and the available intelligence supports a near-term patching priority rather than an emergency response.
Arbitrary code execution inside the Chrome sandbox can be triggered in Google Chrome builds prior to 156.0.8078.73 by a crafted HTML page that exploits a memory-corruption flaw in the Payments component. The CVSS score of 8.8 reflects high confidentiality and integrity impact, but exploitation requires user interaction (UI:R) and the code execution is scoped to inside the sandbox, so host compromise would require an additional sandbox escape. No public exploit or active exploitation is identified at time of analysis, and Google has released a fixed build.
Google Chrome before 156.0.8078.73 contains a use-after-free in its FileSystem component that lets a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) shows a network-reachable, low-complexity issue that requires user interaction, with code execution confined to Chrome's renderer sandbox unless a separate sandbox-escape flaw is chained. Vendor-released patch: 156.0.8078.73; no public exploit was identified at time of analysis, and no CISA KEV entry was supplied.
Use-after-free in Google Chrome's Compositing component (versions prior to 156.0.8078.73) allows remote attackers to corrupt memory and potentially execute arbitrary code inside the renderer sandbox by luring a victim to a crafted HTML page. Exploitation requires no authentication or prior privileges (CVSS 8.8, AV:N/AC:L/PR:N) but does require user interaction, and because the scope is unchanged the resulting code execution stays confined to the sandbox, so a separate sandbox escape would be needed to reach the host OS. The trigger mechanism inside the compositing code path is not described in the available sources; no public exploit has been identified at time of analysis, and Google has shipped a fixed build in the stable channel.
Use-after-free in PDFium, the PDF rendering engine bundled with Google Chrome, allows remote, unauthenticated attackers to potentially execute arbitrary code within the renderer sandbox when a victim renders a crafted HTML page in Chrome builds prior to 156.0.8078.73. The issue is rated high priority for this week's patch cycle rather than an emergency, a vendor fix exists in Chrome 156.0.8078.73, and no public exploit was identified at time of analysis. Per the vendor description, code execution is confined to the renderer sandbox; full host compromise would require chaining a separate sandbox-escape vulnerability that is not part of this CVE.
Improper input validation in Chrome's ReadingList component (fixed in 156.0.8078.73) lets a remote attacker who convinces a victim to open a crafted HTML page run arbitrary code inside the renderer sandbox. No authentication or prior privileges are needed, but user interaction is mandatory and the impact is confined to the sandbox - escaping to the host would require chaining a separate sandbox-escape flaw. No public exploit code or CISA KEV entry is reported, and the vendor considers the issue High severity in Chromium; the practical risk is real but not a drop-everything emergency given the sandbox boundary and the fact that a fixed build is already available.
Use-after-free in Google Chrome's Modularization component before 156.0.8078.73 allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms no authentication is required, but exploitation hinges on the target loading the attacker's HTML, and the impact is bounded by Chrome's sandbox - this flaw alone does not give control of the host operating system, so a separate sandbox escape would be needed for full device compromise. Chromium rates it High (CVSS 8.8), and no public exploit code or confirmed active exploitation is identified in the available data; the priority call is 'this_week', positioning it as a genuine priority within the normal Chrome patching cycle rather than a drop-everything emergency.
A use-after-free in Chrome's Animation component before 156.0.8078.73 lets a remote attacker who convinces a user to load a crafted HTML page potentially execute arbitrary code inside the renderer sandbox. No authentication is required, but user interaction is the limiting factor, and code execution remains confined to the sandbox - escaping to the host demands a separate sandbox-escape chain. Google rates the Chromium severity Medium while the CVSS vector scores 8.8; the flaw was fixed in the vendor's stable channel update and no public exploit code has been identified at time of analysis.