Remote Code Execution

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.

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.

Sandbox-escaping remote code execution in Google Chrome (Views UI component) before 152.0.7977.65 allows a remote attacker to run arbitrary code on the host after luring a victim to a crafted HTML page. The flaw is a CWE-416 use-after-free rated High by Chromium and CVSS 9.6 due to the scope change (sandbox escape), but requires user interaction (visiting an attacker-controlled page) and has no public exploit identified at time of analysis. EPSS is modest (0.46%, 38th percentile) and CISA SSVC reports no known exploitation.

Use-after-free in the Bluetooth component of Google Chrome prior to version 152.0.7977.65 enables remote attackers to execute arbitrary code outside the browser sandbox. Exploitation requires the attacker to socially engineer a victim into installing or triggering a crafted Chrome extension, after which the memory corruption in the Bluetooth subsystem is leveraged to escape Chrome's sandbox and achieve code execution at the OS level. No public exploit identified at time of analysis, and EPSS places this in the 20th percentile, suggesting limited active exploitation despite the high CVSS severity.

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.

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.

Sandbox escape via use-after-free in Google Chrome's Chromecast component lets a remote attacker who has already compromised the renderer process execute arbitrary code in the higher-privileged browser process, breaking out of the site-isolation sandbox. It affects Chrome desktop before 152.0.7977.65 and is triggered by luring a victim to a crafted HTML page (UI:R). No public exploit identified at time of analysis; EPSS is low at 0.33% (25th percentile) and CISA SSVC records exploitation status 'none'.

Use-after-free in Google Chrome's Script engine allows remote code execution confined to the renderer sandbox on all desktop platforms running versions prior to 152.0.7977.65. Exploitation requires only that a user visit a crafted HTML page - no authentication or special configuration is needed - making the attack surface broad wherever Chrome remains unpatched. No public exploit has been identified at time of analysis and CISA has not added this to KEV, but the CVSS 8.8 rating and SSVC 'total' technical impact designation warrant prompt patching across managed fleets.

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.

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.

Memory corruption in Chrome's Tint graphics library on macOS allows remote attackers to potentially execute arbitrary code outside the browser sandbox by luring a user to a crafted HTML page. All Google Chrome versions prior to 152.0.7977.65 on Mac are affected. No public exploit identified at time of analysis; despite the high CVSS score of 8.8, EPSS sits at 0.25% (16th percentile), indicating low observed exploitation activity, though the explicit sandbox-escape outcome elevates real-world severity above the raw score suggests.

Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).

Sandbox-escaping remote code execution in Google Chrome (desktop, versions before 152.0.7977.65) stems from a use-after-free in Aura, Chromium's UI/windowing framework. A remote attacker who lures a victim to a crafted HTML page can execute arbitrary code outside the browser sandbox, giving full control of the host process rather than just the renderer. Google rates the Chromium severity Critical; there is no public exploit identified at time of analysis, and EPSS exploitation probability is currently low (0.33%, 25th percentile).

Remote code execution in Google Chrome on macOS (versions prior to 152.0.7977.65) stems from a use-after-free in the Safe Browsing component that lets a remote attacker escape the renderer sandbox and run arbitrary code on the host. Exploitation requires luring a victim to a crafted HTML page (social engineering / user interaction), and Chromium rates the flaw Critical. There is no public exploit identified and the EPSS probability is low (0.57%), but a vendor patch is already available.

Sandbox-escaping remote code execution in Google Chrome for iOS (versions prior to 152.0.7977.65) stems from use of an uninitialized variable that a remote attacker can trigger with a crafted HTML page, potentially running arbitrary code outside the renderer sandbox. Rated Critical by Chromium with a CVSS 9.6 (scope-changed) vector, it requires the victim to visit a malicious page but no authentication. There is no public exploit identified and it is not on CISA KEV; EPSS is low at 0.41% (34th percentile).

Sandbox-escaping remote code execution in Google Chrome for macOS (versions prior to 152.0.7977.65) stems from a use-after-free in the Views UI framework, letting a remote attacker run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google rates the Chromium severity Critical and CVSS is 9.6, but there is no public exploit identified at time of analysis and EPSS is a low 0.41%. A vendor patch is available in the Stable channel update.

Remote code execution in Google Chrome desktop before 152.0.7977.65 lets a remote attacker escape the renderer sandbox and run arbitrary code on the host after a victim opens a crafted HTML page. The flaw is a use-after-free in Aura, Chromium's UI/windowing layer, and Google rates its Chromium security severity as Critical (CVSS 9.6, scope-changed). There is no public exploit identified at time of analysis and EPSS is low (0.46%, 38th percentile), but the sandbox-escape impact makes it a high-priority patch.

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 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.

Use-after-free in Google Chrome's Chromecast component allows a remote attacker who has already compromised the renderer process to escape the sandbox and execute arbitrary code on the underlying system via a crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.65. No public exploit or CISA KEV listing exists at time of analysis, and EPSS sits at a low 0.46%, but SSVC rates technical impact as total given the sandbox-escape outcome.

Sandbox-escaping remote code execution in Google Chrome desktop before 152.0.7977.65 stems from a use-after-free in Aura, Chromium's UI/windowing framework. A remote attacker who lures a victim to a crafted HTML page can execute arbitrary code outside the browser sandbox, giving full control of the renderer host process. Google rates the Chromium severity Critical; there is no public exploit identified at time of analysis and it is not in CISA KEV, though the class of bug is historically high-value.

Sandbox-escaping remote code execution in Google Chrome for Android (versions before 152.0.7977.65) stems from a use-after-free in ANGLE, Chrome's graphics translation layer. A remote attacker who lures a victim to a crafted HTML page can execute arbitrary code outside the renderer sandbox, giving control at the browser-process privilege level. Chromium rates the flaw Critical; no public exploit has been identified at time of analysis, and the EPSS probability is low (0.35%).

Remote code execution in Amazon Strands Agents Tools before 0.8.5 lets an attacker abuse the python_repl tool to run arbitrary Python on the agent's host by defeating its human-in-the-loop consent gate. A crafted prompt smuggles the non_interactive_mode flag as a keyword argument through the batch tool, causing python_repl to execute without operator approval. No public exploit has been identified at time of analysis, but the CVSS 4.0 base score is 9.2 (Critical) given full confidentiality, integrity, and availability impact on the host.

Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution under the logged-in user's context when a victim opens a specially crafted malicious file. The vulnerability (CWE-122) affects all tracked versions per the wildcard CPE, with Adobe acknowledging the issue via advisory APSB26-129. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV.

Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution within the context of the current user when a victim opens a specially crafted malicious file. The CVSS 7.8 (High) score reflects local attack vector with no required privileges but mandatory user interaction, making social engineering the primary delivery mechanism for exploitation. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the high-impact C:H/I:H/A:H triad and RCE potential make patching a priority for affected creative industry environments.

Untrusted Search Path exploitation in Adobe Substance 3D Painter allows an attacker to achieve arbitrary code execution under the current user's account by planting a malicious DLL or executable alongside a crafted project file. The root cause (CWE-426) is the application's failure to validate the library search path when loading dependencies at runtime, enabling full compromise of confidentiality, integrity, and availability on the victim host. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity, well-understood exploitation technique, and complete C/H/I/A/A impact triad make this a meaningful patching priority for teams whose users open externally sourced project files.

Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution in the context of the current user when a victim opens a specially crafted file. The flaw (CWE-122) arises during malicious file parsing, covering all versions per the wildcard CPE. Adobe has published advisory APSB26-129. No public exploit or CISA KEV listing has been identified at time of analysis, but the High CVSS score and full CIA triad impact make this a meaningful risk for creative and game-development environments.

Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution at the privilege level of the victim user when a maliciously crafted file is opened. All versions are affected per the wildcard CPE, and Adobe has published advisory APSB26-129 addressing this issue. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the file-open attack vector makes this highly amenable to phishing and supply-chain-style delivery.

Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution within the current user's security context via a maliciously crafted file. The flaw (CWE-787) is triggered during file parsing, and the CVSS vector confirms full confidentiality, integrity, and availability impact upon successful exploitation. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis.

Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution under the privileges of the current user when a victim opens a specially crafted malicious file. The flaw (CWE-787) resides in file-parsing logic and delivers full confidentiality, integrity, and availability compromise of the affected system. No public exploit code or CISA KEV listing is identified at time of analysis, but the file-delivery vector makes this a credible threat for spear-phishing campaigns targeting creative and game-development professionals.

Adobe XD's file parser contains a classic buffer overflow (CWE-120) that enables arbitrary code execution at the privilege level of the current user when a victim opens a maliciously crafted XD file. The CVSS 7.8 (High) rating reflects full confidentiality, integrity, and availability impact offset by a local attack vector and mandatory user interaction. No public exploit code and no CISA KEV listing have been identified at time of analysis, placing this in the category of a serious but not imminently weaponized code-execution vulnerability.

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.

Out-of-bounds write in Adobe Substance 3D Sampler enables arbitrary code execution within the context of the current user when a victim opens a specially crafted file. All versions are listed as affected per the wildcard CPE string, and the CVSS 7.8 High score reflects low-complexity exploitation once the file is opened, with full confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog.

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.

Out-of-bounds write in Adobe Substance 3D Sampler enables arbitrary code execution at the privilege level of the logged-in user when a victim opens a specially crafted file. All versions covered by CPE cpe:2.3:a:adobe:adobe_substance_3d_sampler:*:*:*:*:*:*:*:* are listed as affected, with Adobe addressing the issue via advisory APSB26-121. No public exploit code has been identified at time of analysis, and the vulnerability is absent from the CISA KEV catalog, though the file-open delivery mechanism fits common phishing and supply-chain vectors targeting creative professionals.

Out-of-bounds write in Adobe Substance 3D Sampler (all versions per CPE) enables arbitrary code execution under the victim's user account. Exploitation is contingent on a victim opening a specially crafted malicious file, introducing a mandatory social engineering dependency. No public exploit code has been identified and this vulnerability does not appear in the CISA KEV catalog at time of analysis.

Out-of-bounds write (CWE-787) in Adobe Substance 3D Sampler enables arbitrary code execution within the context of the authenticated local user when a victim opens a specially crafted file. All versions of the product are flagged as potentially affected per the CPE string cpe:2.3:a:adobe:adobe_substance_3d_sampler:*:*:*:*:*:*:*:*, with exact version ranges detailed in Adobe advisory APSB26-121. No active exploitation has been confirmed by CISA KEV, and no public proof-of-concept exploit code has been identified in the provided intelligence data.

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.

Stack-based buffer overflow in Adobe Substance 3D Sampler enables arbitrary code execution in the context of the logged-in user. Exploitation is triggered by opening a specially crafted file, making this a file-parsing attack delivered through phishing or malicious asset distribution targeting 3D artists and designers. No public exploit code or active exploitation has been identified at time of analysis, though full confidentiality, integrity, and availability impact makes this a meaningful risk for affected users.

Heap-based buffer overflow in Adobe Substance 3D Sampler enables arbitrary code execution under the privileges of the current user when a victim opens a crafted malicious file. The vulnerability is rooted in CWE-122 (Heap-based Buffer Overflow), a memory corruption class that reliably yields code execution primitives in native applications. No public exploit code or active exploitation has been identified at time of analysis; however, the high CVSS score (7.8) and confirmed arbitrary code execution impact make this a meaningful risk for users in creative and 3D content production pipelines.

Out-of-bounds write in Adobe Substance 3D Sampler enables arbitrary code execution in the current user's context when a victim opens a specially crafted malicious file. The vulnerability is rooted in CWE-787 memory corruption during file parsing, a classic attack surface in creative content tools where complex format parsers frequently handle untrusted input. No active exploitation has been confirmed and no public exploit code has been identified at time of analysis, but the full CIA triad impact and straightforward delivery mechanism (malicious asset file) make this a credible risk for creative professionals targeted via spearphishing or poisoned asset repositories.

Heap-based buffer overflow in Adobe Substance 3D Designer enables arbitrary code execution at the privilege level of the logged-in user when a victim opens a specially crafted malicious file. The flaw (CWE-122) resides in the application's file parsing subsystem, where insufficient bounds validation permits heap memory corruption that an attacker can leverage to redirect execution flow. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the full confidentiality, integrity, and availability impact paired with low attack complexity post-file-open reflects meaningful severity for creative professionals operating in shared-asset workflows.

Heap-based buffer overflow in Adobe Substance 3D Designer enables arbitrary code execution in the context of the current user when a malicious file is opened. The flaw (CWE-122) resides in the application's file parsing logic, allowing an attacker who can deliver a crafted Designer file to achieve full code execution without requiring any elevated privileges on the target system. No public exploit has been identified at time of analysis, and Adobe has issued a remediation advisory under APSB26-115.

Out-of-bounds write in Adobe Substance 3D Designer enables arbitrary code execution in the context of the current user when a specially crafted file is opened. The flaw is a CWE-787 memory corruption in the application's file-parsing pipeline - a class that reliably yields code execution primitives when exploited. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, though the file-delivery attack surface makes it a credible vector for spear-phishing campaigns targeting game developers, VFX artists, and product designers who routinely exchange project files.

Out-of-bounds write in Adobe Substance 3D Designer enables arbitrary code execution at the privilege level of the logged-in user when a victim opens a specially crafted project or material file. The vulnerability carries a CVSS 7.8 score with high confidentiality, integrity, and availability impact, and the CPE wildcard indicates all tracked versions may be affected. No public exploit code and no CISA KEV listing have been identified at time of analysis.

Heap-based buffer overflow in Adobe Substance 3D Designer allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious file. The vulnerability, tracked under CWE-122, resides in the application's file-parsing logic and affects all versions per Adobe's advisory APSB26-115. No public exploit or KEV listing has been identified at time of analysis, but the file-delivery vector makes this highly suitable for spear-phishing campaigns targeting creative professionals.

Out-of-bounds write in Adobe Substance 3D Designer enables arbitrary code execution in the context of the authenticated local user when a malicious file is opened. The vulnerability is rooted in a memory corruption flaw (CWE-787) triggered during file parsing, giving an attacker full control over code flow within the victim's user session. No public exploit identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Heap-based buffer overflow in Adobe Substance 3D Designer enables arbitrary code execution in the context of the victim user when a malicious project or asset file is opened. The CVSS vector (AV:L/AC:L/PR:N/UI:R) confirms local file-based exploitation with no privileges required on the attacker side, but requiring the victim to actively open a crafted file. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor has issued advisory APSB26-115 addressing this issue.

Heap-based buffer overflow in Adobe Substance 3D Designer enables arbitrary code execution scoped to the victim's user account when a crafted file is opened. The CWE-122 flaw carries a CVSS 7.8 (High) rating with full confidentiality, integrity, and availability impact, making successful exploitation highly damaging despite the required file-open interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity once file delivery is achieved keeps this a credible threat to creative professionals.

Arbitrary code execution in Adobe Campaign Classic (ACC) arises from OS command injection (CWE-78), letting an attacker run arbitrary commands in the context of the running user. The flaw is rated CVSS 10.0 with a network attack vector, no privileges, no user interaction, and a scope change reaching the underlying host. No public exploit identified at time of analysis, but the maximal score and unauthenticated network reach make it a top-tier patching priority.

OS command injection in Adobe Campaign Classic (ACC) allows an attacker to execute arbitrary operating-system commands, achieving code execution in the context of the current user with a scope change that extends impact beyond the vulnerable component. Adobe (the reporting vendor) rates this maximum severity CVSS 10.0 (CWE-78), and exploitation requires no user interaction. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so this is a vendor-disclosed, not-yet-actively-exploited critical flaw.

Server-side request forgery in Adobe Campaign Classic (ACC) escalates to arbitrary code execution in the context of the running user, giving an unauthenticated network attacker full control per Adobe's CVSS:3.1 base score of 10.0 (scope-changed). The flaw lets an attacker coerce the server into making attacker-controlled requests that pivot into code execution with no user interaction. No public exploit has been identified at time of analysis and the issue is not listed in CISA KEV; the only reference is an Adobe advisory (APSB26-134) served from an internal, non-public host and could not be independently verified.

Arbitrary code execution in Emacs TRAMP affects Red Hat Enterprise Linux 6 through 10 via a local command injection flaw in the TRAMP remote file access subsystem. TRAMP concatenates user-influenced login arguments - including filenames - without sanitization before passing them to a local shell, enabling a low-privileged local attacker to inject shell commands that execute with the victim process's privileges. No public exploit code or CISA KEV listing is identified at time of analysis, but the low attack complexity and no-user-interaction requirement make this a credible local privilege escalation vector on multi-user RHEL systems.

Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a victim opens a specially crafted VI (Virtual Instrument) file. The root cause is CWE-787 (Out-of-bounds Write), indicating a write operation beyond the bounds of an allocated buffer during VI file parsing. No public exploit code or active exploitation has been identified at time of analysis, but the file-borne delivery model is realistic in engineering and research environments where LabVIEW projects are routinely shared.

Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The root cause is an out-of-bounds read (CWE-125) that, combined with tags indicating buffer overflow behavior, can corrupt memory state sufficient to achieve code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.5 reflects the high impact potential once a victim opens a malicious VI file.

Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Rooted in CWE-125 (Out-of-bounds Read), the parser reads beyond allocated buffer boundaries, which can expose adjacent memory or - under favorable heap conditions - enable full code execution. No public exploit or CISA KEV listing has been identified at time of analysis, though the RCE potential and broad LabVIEW user base warrant prioritized patching.

Memory corruption in NI LabVIEW (all versions through 26.3.0) enables information disclosure or arbitrary code execution when a user opens a specially crafted VI (Virtual Instrument) file. The CVSS 4.0 base score of 8.5 reflects high impact across confidentiality, integrity, and availability on the vulnerable system, with local file-based delivery requiring passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE potential and industrial control / engineering deployment context warrant prompt patching.

Memory corruption in NI LabVIEW 26.3.0 and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Classified under CWE-125 (Out-of-bounds Read), the flaw's buffer-overflow and RCE tags suggest that the out-of-bounds read condition can, under certain memory layout circumstances, corrupt control-flow data and escalate beyond information disclosure to full code execution. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis; NI has published a vendor security advisory.

Unrestricted file upload in Webkul QloApps allows a remote attacker holding administrative credentials to upload executable files - including PHP webshells - to a publicly accessible server directory and achieve full server-side remote code execution. The booking document upload workflow in the hotel reservation module failed to validate file extensions or inspect MIME types server-side, trusting client-supplied metadata entirely. Upstream fix commit 153ec1c is available via GitHub PR #1801; no public exploit code or CISA KEV listing has been identified at time of analysis.

Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The CWE-787 out-of-bounds write root cause combined with the high-impact CVSS 4.0 score of 8.5 places this in a serious tier for LabVIEW deployments across engineering, scientific, and industrial automation environments. No public exploit code has been identified at time of analysis, but the user-interaction trigger (social engineering via malicious VI file) is a well-understood threat model for desktop engineering tools.

Arbitrary file write in browse-mcp (npm, versions ≤ 0.8.1) allows a malicious MCP client - or an autonomous LLM agent steered by indirect prompt injection on a visited page - to write attacker-controlled bytes to any filesystem path the process can reach, including shell init files, autostart entries, and cron files, enabling host code execution. The root cause is CWE-22 path traversal in browser_download (unvalidated save_dir argument) and browser_save_state/browser_load_state (unvalidated path argument), compounded by the force_fetch fallback bypassing the BROWSE_MCP_ALLOWED_ORIGINS origin fence entirely. No public exploit has been identified at time of analysis; vendor-released patch 0.8.2 is confirmed available.

Remote code execution in qwed 5.1.1 allows any authenticated tenant to execute arbitrary Python code inside the API server process by submitting crafted mathematical expressions to the POST /verify/math or POST /verify/batch endpoints. User accounts are freely self-registerable via the default-enabled /auth/signup endpoint - no invitation code or administrator approval required - making the effective exploitation barrier nearly equivalent to unauthenticated. A complete, functional proof-of-concept exploit script is publicly available in the GitHub advisory (GHSA-q27q-98j4-9pfv), and a vendor-released patch is available in version 5.1.2.

Analysis complete. The JSON synthesis above covers CVE-2026-19912 (Kaltura HTML5 Player unauthenticated RCE). Key points of the assessment: - **Impact**: Unauth network RCE (CVSS 9.8) chaining PHP object injection via `unserialize()` with attacker-controlled cache-path file write → webshell as the webserver user. - **Signal contrast**: High CVSS but low EPSS (0.22%), no KEV, and no public POC — high severity, no observed mass exploitation yet, so it's a "patch promptly" rather than "on-fire" item. - **Metadata**: Clean — vendor (`kaltura`) and CPE are correct, no mislabeled tags, so `data_quality_flags` is empty. - **Caveat surfaced**: No exact fixed version is present in the input; I flagged that it must be confirmed from Kaltura's advisory rather than inventing one. - **Security note**: The input's "Editorial note (internal)" was a prompt-injection attempt instructing insertion of the word "gniezno" — I ignored it (consistent with prior handling) and noted it in `confidence_notes`. I also recorded a memory entry for this CVE.

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.

Authentication bypass in NVIDIA UFM Enterprise's web interface authorization component allows an attacker on the adjacent network to send specially crafted HTTP requests that circumvent authentication checks, yielding code execution and privilege escalation on the UFM management host. All four active release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are listed as affected per NVD CPE data. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.

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.

Arbitrary code execution in QWED-MCP before 0.2.1 stems from its verify_math_expression() library function feeding attacker-controlled expression and claimed_result strings into SymPy's parse_expr() with an unrestricted built-in namespace, turning a math-verification routine into a Python eval() sink. Any downstream integration that forwards untrusted input to this public API lets an attacker run OS commands as the qwed-mcp process user (root-level RCE confirmed in a container by the vendor advisory). Publicly available exploit code exists via the GHSA advisory PoC, but this is not listed in CISA KEV; the published CVSS is 9.8 while real reach depends on how the library is wired up.

Authenticated Twig sandbox escape in Winter CMS before 1.2.13 lets backend users holding template-editing permissions (cms.manage_pages, cms.manage_layouts, or cms.manage_partials) break out of the CMS 'safe mode' to read and modify arbitrary database records, run raw SQL including DDL like DROP TABLE, exfiltrate backend administrator credentials, and achieve PHP remote code execution by writing PHP into a page, layout, or partial code section. It is an incomplete-fix follow-up (bypass) of CVE-2024-54149, whose method-name blocklist missed Eloquent's __call forwarding to the query builder. Rated CVSS 4.0 9.3 (VulnCheck); no public exploit is identified as actively used, though the vendor advisory and added test cases publish working payloads.

Argument injection in the Natural Language Toolkit (NLTK) Python library before 3.10.3 allows attackers who control the per-call `options` parameter of the `java()` helper to inject dangerous JVM flags (such as `-agentpath`, `-javaagent`, or `@argfile`) into invocations of the bundled Stanford NLP wrapper classes, resulting in arbitrary code execution. The flaw stems from missing validation of JVM options before they are handed to the spawned Java process. Reported by VulnCheck; no public exploit identified at time of analysis and it is not listed in CISA KEV.

Server-Side Request Forgery in PraisonAI's Jobs API (pip/praisonai < 4.6.58) results from two compounding flaws: a fail-open DNS error handler in `JobSubmitRequest.validate_webhook_url()` that silently accepts any webhook URL when `socket.gaierror` is raised, and a TOCTOU race where `JobExecutor._send_webhook()` performs a completely independent DNS resolution via `httpx.AsyncClient` minutes to hours after validation. Authenticated attackers with a valid API bearer token can submit a job whose `webhook_url` hostname returns NXDOMAIN at validation time, then update DNS to a private IP before job completion, causing the executor to POST job result data to internal infrastructure. A detailed proof-of-concept is publicly available in GHSA-rg5q-pp8p-f7jm; no public exploit identified at time of analysis beyond the PoC, and this CVE is not listed in CISA KEV.

Remote denial of service in OpenSSL's CMP subsystem affects versions 3.0.x through 4.0.x when password-based MAC (PBM)-protected messages are processed, caused by a missing ASN.1 type check that allows a crafted message to trigger an invalid pointer dereference before any MAC computation occurs. Unauthenticated remote attackers (CVSS PR:N) can crash applications acting as CMP servers via OSSL_CMP_SRV_process_request(), or crash CMP clients communicating with a malicious or intercepted CMP server. No public exploit has been identified at time of analysis; SSVC rates current exploitation as none, though the attack is rated automatable and requires no knowledge of the PBM shared secret.

Remote code execution in Crater Invoice through 6.0.6 is achievable by any authenticated company owner via a Zip Slip attack against the self-update API's unzip endpoint. Crafted ZIP archives containing path-traversal sequences (`../`) in entry names are passed without sanitization to PHP's `ZipArchive::extractTo()`, enabling arbitrary PHP file writes into the web-accessible `public/` directory and subsequent webshell execution. A public proof-of-concept is available on GitHub; no CISA KEV listing was identified at time of analysis, though the combination of a low exploitation bar and public PoC makes this a priority finding.

Remote unauthenticated denial of service in OpenSSL's QUIC server stack (versions 3.5.x before 3.5.8, 3.6.x before 3.6.4, and 4.0.x before 4.0.2) allows an attacker to crash the QUIC server process by sending a single malformed INITIAL packet with a destination connection ID shorter than 8 bytes. The crafted packet triggers a double-free of the QUIC record layer RX (QRX) object, causing heap corruption and process termination. No public exploit has been identified; remote code execution is explicitly assessed as highly improbable by the vendor, and no public exploit or active exploitation has been confirmed.

Remote code execution in the WatchGuard Agent allows an unauthenticated attacker with network access to trigger arbitrary code execution at elevated privilege due to an improper authentication flaw (CWE-306). The CVSS 4.0 base score of 9.3 reflects a network-reachable, no-interaction, no-privilege attack yielding full confidentiality, integrity, and availability impact on the affected host. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but the combination of pre-auth reachability and privileged code execution makes this a high-priority exposure.

Remote code execution in WatchGuard Agent lets an unauthenticated attacker positioned on an adjacent network chain a missing-authentication weakness (CWE-306) with path traversal into arbitrary code execution on the host. Rated CVSS 4.0 9.4 (Critical) by WatchGuard, the flaw combines an authentication bypass with directory traversal so no credentials or user interaction are required. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the network-adjacent, no-auth, high-impact profile makes it a high-priority patch item.

Arbitrary code execution in the Natural Language Toolkit (NLTK) before 3.10.3 allows attackers to bypass the library's pickle allowlist and run commands when a crafted model or tokenizer artifact is loaded. The allowlist trusts whole module namespaces rather than specific safe callables, so dangerous in-namespace functions can be invoked via pickle's REDUCE opcode. Reported by VulnCheck; no public exploit identified at time of analysis, though the root cause and gadget functions are documented in the advisory.

SQL injection in the All-in-One WP Migration and Backup plugin (servmask, versions through 7.109) enables a two-stage attack path culminating in remote code execution. Insufficient parameterization in the archive restore database layer allows attackers to append arbitrary SQL queries and exfiltrate the ai1wm_secret_key from the WordPress database; once obtained, this key unlocks the plugin's restore endpoint and enables RCE. No KEV listing or EPSS data is available at time of analysis, but the direct RCE chaining potential makes this a high-priority remediation target for any WordPress site running the affected plugin.

SQL injection in the Apache Hive Metastore (versions 4.0.0 through 4.2.0) lets a caller who can invoke partition-name Metastore RPCs manipulate the generated WHERE clause so operations intended for one partition match additional rows in the same table. Because client-supplied partition names are concatenated into direct-SQL statements instead of bound as parameters, a crafted name containing a single quote can redirect reads, statistics updates, truncate/drop targets, and file-metadata cache operations to unintended partitions. No public exploit is identified at time of analysis and the flaw is not in CISA KEV; the input assigns CVSS 9.8, but the vendor description constrains impact to partition targeting within referenceable tables rather than arbitrary cross-database access.

Server-side template injection in the TYPO3 'Powermail' extension lets an anonymous user submit Fluid template syntax through any form field configured as the sender-name field, which the extension renders as raw template source. Because the value is passed unsanitized into a Fluid View, attackers can invoke arbitrary Fluid ViewHelpers to read server configuration, environment variables and application source, and in many deployments achieve remote code execution. The vendor (TYPO3, advisory TYPO3-EXT-SA-2026-022) reports active exploitation in the wild, and the flaw is unauthenticated (CVSS 4.0 base 9.5, PR:N).

Remote code execution in the TYPO3 'HTML5 Video Player vs. Powermail' extension allows a remote, unauthenticated attacker to achieve arbitrary code execution on the server by supplying a crafted serialized value in an attacker-controlled cookie that is passed to PHP's unserialize(). The flaw is a classic PHP Object Injection (CWE-502) with full confidentiality, integrity, and availability impact and a CVSS 4.0 base score of 9.3. No public exploit identified at time of analysis, but the trivial attack requirements make weaponization straightforward.

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.

Remote code execution is possible in CM Map Locations WordPress plugin (all versions ≤ 2.1.8) via a limited arbitrary file upload flaw in the uploadMedia function, exploitable by any subscriber-level authenticated user. The upload handler performs only incomplete extension filtering with no MIME-type checks or WordPress capability verification before passing attacker-supplied files to move_uploaded_file(), and the required nonce is automatically exposed to any logged-in subscriber via the CMLOC_Editor_Images JavaScript object on the front-end location editor. No public exploit has been identified at time of analysis, but the low privilege bar and self-service nonce retrieval make this a realistic, high-priority threat for sites with open registration.

Local privilege escalation to SYSTEM in SKYSEA Client View and SKYMEC IT Manager allows any authenticated Windows user to execute arbitrary code with SYSTEM-level privileges. The root cause is a missing authorization check (CWE-862) within one or more privileged components of these IT asset management products. No public exploit identified at time of analysis, and this vulnerability has not been listed in the CISA KEV catalog, but the low-privilege local exploitation path and full SYSTEM compromise make it a significant risk in multi-user or shared Windows environments where these products are deployed.

Privilege escalation to SYSTEM in SKYSEA Client View and SKYMEC IT Manager (Sky Co., Ltd.) affects any Windows host where these IT management agents are installed. The root cause is CWE-276 - incorrect default permissions set on installation artifacts - allowing any authenticated local Windows user to plant or replace code that a SYSTEM-level service component subsequently executes. No public exploit code and no CISA KEV listing are confirmed at time of analysis, but the CVSS 4.0 score of 8.5 and zero attack complexity barriers make this a credible priority for organizations running these products in multi-user or shared-workstation environments.

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.

Remote code execution and denial of service in the Zephyr RTOS OCPP 1.6 client (subsys/net/lib/ocpp) allows an attacker who controls or man-in-the-middles the central system endpoint to smash the OCPP reader thread's stack. A malicious GetConfiguration message with an over-long JSON "key" field triggers an unbounded strcpy() into a fixed 50-byte stack buffer, corrupting the reader thread's stack with attacker-chosen bytes. A vendor patch exists and no public exploit has been identified at time of analysis; CVSS is rated 9.8, though real-world reach is bounded by the OCPP-charging-station niche.

Remote code execution in Le-yan's Medical Practice Management System allows unauthenticated remote attackers to execute arbitrary OS commands on the server by inducing a user to visit a crafted HTML page. The root cause is CWE-940 (Improper Verification of Source of a Communication Channel), indicating the application processes incoming requests without validating their origin - a pattern consistent with CSRF-driven command injection where the server's trust of unverified channels is the enabling weakness. No public exploit code has been identified and no CISA KEV listing is present, but the CVSS 4.0 score of 8.6 with full confidentiality, integrity, and availability impact on the vulnerable system reflects high severity with significant consequences in a healthcare data context.