Out-of-bounds write in Chrome's Crashpad crash-reporting library on Windows, versions prior to 152.0.7977.65, enables sandbox escape and arbitrary code execution when chained with a separate renderer compromise. The flaw (CWE-787) is the second stage of a two-stage exploit: an attacker who has already gained code execution inside the sandboxed renderer can trigger the memory corruption in Crashpad to break the sandbox boundary and execute arbitrary code at Chrome process privilege on the host. No public exploit has been identified at time of analysis and SSVC rates current exploitation as none, though the total technical impact and Windows-wide scope make this a high-priority patch item.
Sandbox escape via incorrect USB authorization in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox through a crafted HTML page combined with social engineering. The attack chain is multi-stage: the USB subsystem fails to correctly authorize renderer-process requests, enabling a scoped privilege escalation out of the sandbox (S:C in CVSS). No public exploit code is identified and SSVC assessment confirms no known exploitation at time of analysis, though successful exploitation would yield total technical impact.
Race condition in Chrome's ReadAloud component allows remote code execution inside the browser sandbox when a user is socially engineered into visiting a crafted HTML page. Affected are all Google Chrome builds prior to 152.0.7977.65 across desktop platforms. The CVSS Scope:Changed metric signals a potential sandbox escape, elevating the impact beyond the renderer process to the underlying system, though EPSS (0.33%) and SSVC exploitation status of 'none' indicate no public exploit activity at time of analysis.
Sandbox escape via use-after-free in Chrome's Chromecast component allows remote code execution outside the browser sandbox on all platforms running Chrome prior to 152.0.7977.65. This is a chained exploit: an attacker must first compromise the renderer process, then leverage the Chromecast UAF to pivot into the browser process and escape Chrome's sandbox via a crafted HTML page. No public exploit code has been identified at time of analysis; Google has released a confirmed fix in version 152.0.7977.65.
Sandbox escape in the WebView component of Google Chrome on Android (prior to version 152.0.7977.65) allows an attacker who has already compromised the renderer process to execute arbitrary code outside the Chrome sandbox on the target device via a crafted HTML page. This CWE-610 externally controlled reference flaw represents the second stage of a chained exploit - requiring a companion renderer exploit to be viable - which substantially raises the real-world exploitation bar despite the CVSS 8.3 High score. No public exploit has been identified at time of analysis, and EPSS places exploitation probability at 0.33% (25th percentile), consistent with no observed active exploitation.
Integer overflow in the Chromecast component of Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to escape the browser sandbox and execute arbitrary code on the underlying operating system via a crafted HTML page. The CVSS score of 8.3 reflects the full scope change (S:C) and complete confidentiality, integrity, and availability impact once the sandbox boundary is crossed, while AC:H acknowledges the mandatory pre-existing renderer compromise required to reach the vulnerable code path. No public exploit has been identified at time of analysis, and EPSS stands at a low 0.30% (22nd percentile), consistent with the elevated exploitation complexity of this chained-attack vulnerability.
Use-after-free in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows enables a remote attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code at the browser or OS level via crafted network traffic. All Chrome versions prior to 152.0.7977.65 on Windows are affected. No public exploit code or CISA KEV listing exists; EPSS is low at 0.28% (20th percentile), but the scope-changing, full-CIA-impact sandbox escape warrants rapid deployment of the available patch.
Sandbox escape via type confusion in Google Chrome's Accessibility component on Windows enables arbitrary code execution outside the browser sandbox. Affecting all Chrome versions prior to 152.0.7977.65 on Windows, the flaw requires an attacker to have already compromised the renderer process - making this a critical second-stage exploit in a multi-step attack chain. No public exploit identified at time of analysis, and EPSS sits at 0.27% (19th percentile), consistent with the high technical bar required for exploitation despite the 8.3 CVSS score.
Sandbox escape via Chromecast in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside Chrome's sandbox through a crafted HTML page. Rated Critical by the Chromium security team, the flaw is a chained exploit requiring a prior renderer compromise plus user interaction, reflected in AC:H and UI:R CVSS metrics. No public exploit identified at time of analysis; EPSS at 0.25% (16th percentile) indicates low current exploitation probability despite the severity rating.
Sandbox escape in Google Chrome for Android (versions prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox by delivering a crafted HTML page to the victim. The vulnerability stems from improper input validation in Chrome's Input subsystem on Android, confirmed by the CVSS scope-change metric (S:C) indicating the exploit crosses the sandbox boundary. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS of 0.25% reflects the low automated exploitation probability attributable to the chained attack requirement.
Sandbox escape in Google Chrome's Printing subsystem prior to 152.0.7977.65 allows an attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox via a crafted HTML page. This is a two-stage, chained exploit: the printing component's failure to validate renderer-supplied input (CWE-20) becomes the second link used to break containment and reach the host OS. No public exploit has been identified at time of analysis, and EPSS is low at 0.25% (16th percentile), consistent with the elevated attack complexity required.
Unauthenticated account takeover in the TYPO3 femanager extension 8.x allows a remote attacker to reset the password of and re-enable any existing frontend user account - including disabled or deleted ones - by exploiting an invitation controller that continues processing after issuing a redirect on invalid input. No prior authentication or user interaction is required. No public exploit code or active exploitation has been identified at time of analysis, but the impact is severe: full account takeover of arbitrary frontend users in any TYPO3 installation running femanager 8.x.
Sandbox escape in Google Chrome prior to 152.0.7977.65 allows a remote attacker who has first compromised the renderer process to break out of Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. Rooted in CWE-863 (Incorrect Authorization), the Chrome sandbox fails to correctly enforce permission checks on requests originating from a compromised renderer, permitting privilege escalation beyond the sandbox boundary. No public exploit code has been identified at time of analysis, and EPSS scores a low current exploitation probability of 0.24% (15th percentile), though the full-compromise impact potential warrants prompt patching across all Chrome desktop deployments.
The femanager extension for TYPO3 CMS incorrectly accepts a regular user confirmation hash - obtainable by any visitor via the public resend-confirmation action - in place of the privileged admin confirmation token when processing account-approval requests. This allows a registrant whose account is pending administrator authorization to self-approve that account, fully bypassing the admin-approval gate. No public exploit code has been identified at time of analysis, but the attack is mechanically trivial given the public exposure of the prerequisite token; the CVSS 4.0 score of 8.3 reflects high confidentiality impact against the vulnerable system.
Authorization bypass in the Grav Flex Objects plugin (versions 1.4.0-1.4.7) allows any user holding page-edit access to render arbitrary registered Flex collections - including the full user account directory - by embedding a shortcode in published pages. The shortcode rendering path entirely omits the `authorize` ACL checks enforced in the admin panel, meaning lower-privileged editors can extract sensitive data that would otherwise be restricted to administrators. No public exploit or CISA KEV listing exists at time of analysis, but the low privilege bar and network accessibility make this a credible insider or compromised-account threat on multi-author Grav installations.
Sandbox escape via GPU race condition in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to execute arbitrary code outside the browser sandbox through a crafted HTML page. The flaw is a time-of-check-to-time-of-use (TOCTOU) race condition (CWE-367) in Chrome's GPU component, classified Medium severity by the Chromium team despite a CVSS score of 8.3 - reflecting the mandatory renderer pre-compromise prerequisite that makes this a chained exploit rather than a standalone attack. No public exploit has been identified and EPSS probability is 0.20% (10th percentile), consistent with this vulnerability's role as a sophisticated second-stage primitive.
Sandbox escape via race condition in Google Chrome's FileSystem component (prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox through a crafted HTML page. This is a scope-changing exploit chain primitive - it operates as a second-stage attack requiring renderer access first, not a standalone unauthenticated RCE. No public exploit code is identified at time of analysis, and EPSS sits at 0.20% (10th percentile), reflecting low current exploitation probability despite the High CVSS score.
Server-side request forgery in Ech0 before version 4.7.3 allows authenticated users to pivot through the application server to reach internal infrastructure, including cloud provider metadata APIs and Kubernetes service endpoints. The root cause is a missing URL-validation call: `fetchPeerConnectInfo` in `internal/service/connect/connect.go` invokes the unguarded `SendRequest` helper rather than the `SendSafeRequest` variant that enforces `ValidatePublicHTTPURL` private-IP blocking. A working proof-of-concept demonstrating AWS IMDSv1 and Kubernetes API enumeration is publicly available in the GHSA advisory; no active exploitation via CISA KEV has been confirmed, though the CVSS 4.0 score of 8.3 with SC:H reflects elevated impact potential for cloud-hosted deployments.
Path traversal via symlink bypass in NLTK corpus readers before 3.10.3 permits disclosure of arbitrary files outside the trusted corpus data root through standard API calls. Affected corpus reader methods - channels(), domains(), and synonyms() - reopen root-derived paths with Python's built-in open() rather than the secure nltk.pathsec.open(), which enforces symlink restrictions. An attacker who can stage symlinked files inside a trusted corpus directory can leverage this gap to read files the NLTK process can access on the host filesystem. No public exploit has been identified at time of analysis, and a vendor-released patch is available in NLTK 3.10.3.
Insecure Direct Object Reference in the TYPO3 femanager extension exposes frontend user profile data - including name, email address, date of birth, and postal address - to any unauthenticated visitor who can reach the Detail or List plugin. The extension's user detail view accepts a caller-supplied user ID without validating that the requested record belongs to the configured or authenticated target, making horizontal privilege escalation trivial via ID enumeration. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
NULL pointer dereference in NVIDIA DGX Spark system firmware enables a local privileged attacker to achieve code execution with scope change into other system components. All versions of the DGX Spark firmware are affected per the wildcard CPE, with potential impacts spanning code execution, privilege escalation, denial of service, information disclosure, and data tampering. No public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware enables a privileged local attacker to corrupt memory and achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. The CVSS scope-change indicator (S:C) is the critical risk amplifier here - successful exploitation can breach the firmware's security boundary and affect components outside it, including potentially the host OS or hypervisor layer. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware permits a locally authenticated, highly privileged attacker to corrupt firmware memory in a way that crosses the firmware's isolation boundary into the broader system. Successful exploitation may yield arbitrary code execution, privilege escalation beyond the initial firmware context, denial of service, information disclosure, and data tampering - all stemming from a single CWE-787 write primitive. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope-changing nature of the CVSS vector (S:C) elevates the potential blast radius significantly for affected AI compute infrastructure.
Remote code execution inside the Chrome sandbox is achievable via a use-after-free in the WebRTC component of Google Chrome prior to 152.0.7977.65, exploitable by an unauthenticated remote attacker through crafted network traffic. The flaw requires high attack complexity (AC:H), constraining opportunistic mass exploitation, and code execution is limited to within the Chrome renderer sandbox, reducing but not eliminating post-exploitation impact. No public exploit code and no active exploitation have been identified at time of analysis, consistent with SSVC Exploitation: none and an EPSS of 0.66%.
Disabled TLS certificate verification in X-AnyLabeling's model downloader exposes all versions prior to v4.0.0-beta.9 to man-in-the-middle model substitution during HTTPS downloads. Because `ssl._create_unverified_context()` disables both hostname checking and certificate chain validation, a network-positioned attacker can serve arbitrary model files without detection. For configurations using .pth/.pt files - including the shipped SAM2, YOLOE, UPN, and open_vision setups - the application calls `torch.load` without `weights_only=True`, so a substituted file achieves arbitrary code execution on PyTorch releases predating the `weights_only` default change. No public exploit was identified at time of analysis and this vulnerability is not listed in CISA KEV.
Local File Inclusion in the Mane WordPress theme (all versions up to and including 1.7) allows unauthenticated remote attackers to include and execute arbitrary server-side PHP files, with a realistic path to full remote code execution when file upload functionality is accessible. The CVSS 8.1 score with AC:H signals that the most severe impact - arbitrary code execution - depends on a specific precondition, most likely an attacker-controlled file already present on the server filesystem. No public exploit has been identified at time of analysis, though the LFI-to-RCE chain on WordPress is a well-understood and widely practiced attack class.
Local File Inclusion in Edge-Themes' Shuffle WordPress theme (all versions through 1.8) exposes WordPress installations to unauthenticated remote code execution. An attacker without any credentials can supply a crafted path parameter to the theme's PHP include logic, causing the server to load and execute arbitrary PHP files - including attacker-uploaded content disguised as images. No public exploit has been identified at time of analysis, but the attack pattern (LFI chained with WordPress media uploads) is well-documented in the ecosystem, and the unauthenticated network vector warrants prompt remediation.
Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) enables unauthenticated remote attackers to include and execute arbitrary PHP files on the server. Rooted in CWE-98 (improper PHP include/require path control), the flaw can be chained with file upload functionality - an attacker uploads a PHP-bearing image or other 'safe' file, then triggers the LFI to execute it - yielding full remote code execution, access control bypass, and sensitive data disclosure. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
PHP Object Injection in the Kalles Addons WordPress plugin (all versions up to and including 1.0.6) allows unauthenticated remote attackers to deserialize untrusted PHP objects via a network-accessible deserialization endpoint. Exploitation is strictly conditional: the plugin itself contains no known POP (Property-Oriented Programming) chain, so real-world impact - ranging from arbitrary file deletion and sensitive data retrieval to remote code execution - only materializes when a separately installed plugin or theme on the same WordPress instance supplies a usable POP chain. No public exploit code and no CISA KEV listing have been identified at time of analysis.
UI misrepresentation in Google Chrome's Browser component prior to 152.0.7977.65 enables a remote attacker to bypass system access restrictions through a crafted HTML page combined with social engineering. The flaw (CWE-451) allows the browser to render misleading UI elements that deceive users into believing they are interacting with a trusted context, enabling restriction bypasses with high confidentiality and integrity impact. No public exploit code or CISA KEV listing exists at time of analysis; vendor patch is available.
Unauthenticated access to the NVIDIA NemoClaw inference server on Linux exposes sensitive model inference data and enables denial of service by adjacent network attackers. The flaw stems from a missing authentication check (CWE-306) on the inference service endpoint, meaning any host on the same network segment can interact with the service without credentials. No active exploitation has been confirmed by CISA KEV and no public exploit code is known at time of analysis, but the low attack complexity and absence of authentication barriers make this straightforward to exploit for any attacker with adjacent network positioning.
Use-after-free in the Mobile component of Google Chrome on iOS prior to 152.0.7977.65 enables remote code execution outside the browser sandbox via crafted network traffic, requiring no user interaction. The sandbox escape elevates the severity beyond a typical renderer bug, as successful exploitation grants attacker-controlled code execution in a context beyond Chrome's sandboxed process. No public exploit identified at time of analysis, and the low EPSS score (0.28%, 20th percentile) suggests exploitation has not yet been observed in the wild despite the high CVSS rating.
Use-after-free in the Chromoting (Chrome Remote Desktop) component of Google Chrome on Windows prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code outside Chrome's sandbox via crafted network traffic. The sandbox-escape outcome is the most critical aspect, elevating the real-world impact beyond a typical renderer flaw to full host-level code execution. No public exploit code has been identified at time of analysis; EPSS places exploitation probability at 0.28% (20th percentile), though the network vector and no-auth-required CVSS signal warrant prompt patching.
Improper Authentication in Apache Tomcat allows a remote, low-privileged attacker to gain authenticated access to applications even when the presented identity does not exist in the configured DataSourceRealm. The flaw is triggered specifically under CLIENT-CERT or SPNEGO authentication schemes, causing Tomcat to grant a session to a non-existent user. No public exploit or CISA KEV listing is present at time of analysis, but the CVSS C:H/I:H impact rating reflects the potential to fully compromise protected application resources if exploited in matching deployments.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
HTML escaping in the hbs Express/Handlebars view engine (versions 2.1.0-4.2.1) is bypassed by the registerAsyncHelper API, enabling stored or reflected cross-site scripting in any Express application that passes attacker-influenced data through an async helper callback. The two-pass rendering pipeline escapes only an opaque placeholder in the first pass, then silently substitutes the raw, unescaped callback return value, affecting cached, uncached, and layout render paths equally. No active exploitation has been confirmed in CISA KEV; the issue is fixed in hbs 4.3.0.
Improper state validation in Google Chrome's Performance component (all versions prior to 152.0.7977.65) enables remote attackers to read memory contents within the Chrome sandbox by luring a user to a crafted HTML page. The scope is contained to the sandbox (S:U), limiting blast radius to in-process data, but sensitive browser state such as cookies, session tokens, or page content may be exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS of 0.22% (13th percentile) corroborates low observed exploitation activity.
Use-after-free in Chrome's Chromoting (remote desktop) component allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox via crafted network traffic, affecting all Chrome versions prior to 152.0.7977.65. The sandbox-escape dimension elevates this beyond a typical renderer vulnerability, as successful exploitation could yield code execution in a broader process context. No public exploit identified at time of analysis and SSVC indicates no observed exploitation, but the technical impact is rated total.
Remote code execution inside the Chrome sandbox is possible through a race condition in the Extensions component, exploitable via crafted network traffic against Google Chrome versions prior to 152.0.7977.65. Despite a CVSS score of 8.1, Chrome's own team rates this vulnerability Low severity - a notable divergence explained by the sandbox constraint: successful exploitation yields in-sandbox code execution rather than full OS-level compromise. No public exploit identified at time of analysis, and SSVC confirms no known active exploitation and that the attack cannot be automated reliably.
Sandbox escape via a TOCTOU race condition in Google Chrome's Start component on Android prior to 152.0.7977.65 allows a local attacker to execute arbitrary code outside Chrome's sandbox. Exploitation requires a co-installed malicious application placed via social engineering, making opportunistic mass exploitation infeasible despite a CVSS base score of 8.1. No public exploit code exists and this vulnerability is absent from CISA KEV; EPSS sits at 0.15% (4th percentile), confirming low observed exploitation pressure. Vendor patch is available at version 152.0.7977.65.
Incorrect authorization in the Drupal Edit in-place field contrib module (versions 0.0.0 through pre-2.1.1) enables authenticated users to perform forceful browsing against field-edit endpoints they lack permission to access, resulting in unauthorized read and write access to protected Drupal field data. The CVSS base score of 8.1 reflects high confidentiality and integrity impact, though real-world risk is tempered by the authentication prerequisite (PR:L) and an extremely low EPSS score of 0.13% (3rd percentile). A vendor-released patch is available; no public exploit identified at time of analysis.
Code injection in NVIDIA Unified Fabric Manager Enterprise's plugin management API allows low-privileged, adjacent-network authenticated users to execute arbitrary commands on the UFM host by submitting a specially crafted API request. All current release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are confirmed affected per vendor-supplied CPE data. Successful exploitation yields code execution, privilege escalation, and information disclosure on a platform that controls InfiniBand fabric infrastructure, amplifying downstream impact on managed HPC and AI compute clusters. No public exploit code or CISA KEV listing has been identified at time of analysis.
OS command injection in NVIDIA NemoClaw for Linux allows a local low-privileged attacker to execute arbitrary operating system commands through the application's status and logs plugin command interfaces. The CVSS 7.8 score reflects high impact across confidentiality, integrity, and availability with low attack complexity and no user interaction required. No public exploit identified at time of analysis, and no CISA KEV listing observed, but the fully unscopeed local impact makes this a meaningful risk on multi-tenant or shared Linux systems running NemoClaw.
OS command injection in NVIDIA NemoClaw's NIM management component on Linux enables a local authenticated attacker to execute arbitrary operating system commands with the privileges of the targeted process. All versions of NemoClaw are indicated as affected per NVD CPE data (wildcard version range). Successful exploitation can result in full code execution, persistent data tampering, sensitive information disclosure, and denial of service on the host. No public exploit code or CISA KEV listing has been identified at time of analysis.
OS command injection in NVIDIA NemoClaw's command-line interface on Linux enables a local low-privileged attacker to execute arbitrary operating system commands, leading to full compromise of confidentiality, integrity, and availability. All versions of NemoClaw appear affected per the CPE wildcard (*), and the vulnerability is rooted in improper neutralization of user-supplied input passed to shell commands (CWE-78). No public exploit code and no CISA KEV listing have been identified at time of analysis, limiting current real-world risk primarily to environments with untrusted local users.
OS command injection in NVIDIA NemoClaw's Telegram bridge component on Linux enables a local attacker with low-privileged access to execute arbitrary operating system commands. Exploitation yields full confidentiality, integrity, and availability compromise on the affected host, with potential for privilege escalation beyond the invoking user. No active exploitation is confirmed in CISA KEV and no public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) and minimal privilege requirement (PR:L) lower the practical bar for exploitation once local access is obtained.
Server-side template injection in Compliance-Trestle's custom Jinja2 include tags (`mdsection_include` and `md_clean_include`) allows a low-privileged local attacker to achieve arbitrary code execution when attacker-controlled OSCAL data containing Jinja2 syntax is processed during template rendering. All versions prior to 3.12.4 and the 4.0.0-4.0.3 line are affected; the fix is version 4.1.0. No CISA KEV listing or standalone public exploit has been identified at time of analysis, though security test payloads demonstrating the RCE gadget chain are present in the upstream fix commits.
Heap-based buffer overflow in Adobe Substance 3D Sampler enables arbitrary code execution in the context of the logged-in user when a victim opens a specially crafted malicious file. The attack surface is local - an attacker must deliver and persuade a target to open a weaponized file, a pattern consistent with spear-phishing or watering-hole distribution targeting creative professionals. No public exploit code or CISA KEV listing has been identified at time of analysis.
Heap-based buffer overflow in Adobe Substance 3D Sampler enables arbitrary code execution in the context of the victim user when a malicious file is opened. The vulnerability carries a CVSS 7.8 (High) rating with full confidentiality, integrity, and availability impact on the vulnerable system. No public exploit code or active exploitation has been identified at time of analysis; however, the file-open trigger and broad version coverage (all versions per CPE) make this a credible threat to creative professionals using the software.
Heap-based buffer overflow in Adobe Substance 3D Sampler enables arbitrary code execution in the context of the authenticated local user when a victim opens a specially crafted malicious file. The vulnerability carries a CVSS 3.1 score of 7.8 (High), with full confidentiality, integrity, and availability impact on the affected system. No public exploit code or active exploitation has been identified at time of analysis, though the file-parsing attack surface is a well-understood target for threat actors.