RCE
Monthly
Local DLL search-order hijacking in the GeoVision GV-Remote E-Map Windows desktop application allows an attacker who already holds a local foothold with write access to a directory the application searches to execute arbitrary code in the security context of the GV-Remote E-Map process. The weakness is CWE-427 and is scored CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so it is not remotely exploitable and requires host-local write permission plus a normal application launch for the hijacked library to load. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, and the practical risk is largely determined by whether the application's install and working directories are ACL-restricted against standard users.
Opening an attacker-crafted Affinity document in Affinity by Canva versions prior to 3.3.0 can trigger a stack-based buffer overflow that may lead to arbitrary code execution on the victim's endpoint. Exploitation is not remote or automatic: it requires the user to open the malformed document (UI:R) on a machine where Affinity is installed, and attack complexity is assessed as high (AC:H), reflecting the difficulty of turning the stack corruption into reliable code execution in the presence of modern stack and memory protections. No confirmed active exploitation (CISA KEV) and no public exploit code have been identified at the time of analysis, and the risk is genuine but not top-tier - it is confined to endpoints that handle untrusted Affinity files.
Improper neutralization of newline sequences in NetworkManager-fortisslvpn credential handling allows a local user who can create or modify a FortiSSL VPN connection profile to inject directives that the root-privileged VPN helper executes, resulting in local privilege escalation to root. The flaw is scored 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and was reported by Ubuntu, with Red Hat tracking it through its CVE page and Bugzilla 2533640 against an upstream tracking item in the archived GNOME GitLab project. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so risk is concentrated on multi-user Linux hosts where the plugin is installed and ordinary console users are permitted by policy to configure VPN connections.
Server-side template injection in Craft CMS 5.10.0 through 5.10.12 allows an authenticated low-privilege control-panel user with edit rights on even a single element type to execute arbitrary PHP code and fully compromise the server. The bug is an incomplete fix for CVE-2026-55794: the Controller::getPostedRedirectUrl() to View::renderObjectTemplate() redirect sink stayed unsandboxed, and the same patch introduced a self-signing oracle in Cp::elementLabelHtml(); because Craft/Yii HMAC tokens are not bound to a parameter name, a token minted over attacker-controlled Twig for returnUrl can be replayed as the redirect POST parameter. Exploitation requires a valid CP account with element-edit permissions (PR:L, no user interaction); no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor-released patch is Craft CMS 5.10.13.
Code injection into the quay-builder-qemu release workflow through supply-chain compromise of the third-party GitHub Action `Noelware/docker-manifest-action`, which the workflow references by a mutable branch instead of a pinned immutable commit SHA. An attacker who first subverts that upstream action can execute arbitrary code inside the release pipeline, exfiltrating sensitive registry credentials or publishing malicious container images, with severity amplified because the workflow also exposes the default GITHUB_TOKEN. This is a CI/CD build-pipeline flaw rather than a defect in deployed Quay instances and is not directly exploitable against Quay itself; no public exploit code was identified at time of analysis, and the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H reflects high attack complexity because successful exploitation depends on first compromising an external dependency and only triggers when the release workflow executes.
Unauthenticated arbitrary Python module import in djust before 1.0.7 lets any client that can reach the WebSocket or SSE mount endpoint force the server to import a module chosen by a client-supplied dotted path, executing that module's import-time side effects before any LiveView subclass check or per-view authentication occurs. The LIVEVIEW_ALLOWED_MODULES allowlist that should constrain this lookup is fail-open (the check is skipped when the setting is unset, which is the framework default) and uses loose startswith matching, so the flaw is reachable in a default configuration; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Impact is bounded by what is already installed and importable on the host: guaranteed outcomes are denial of service (import bombs, expensive dependency trees) and a module/class enumeration oracle exposed through distinct error strings, escalating to RCE-by-proxy where a suitably side-effectful module exists. No public exploit has been identified at time of analysis - the maintainer retains the reproducer privately - and there is no CISA KEV listing.
Unsafe deserialization in the opt-in kedro_datasets_experimental.pytorch.PyTorchDataset connector (kedro-datasets versions 5.0.0 through <9.5.0) allows code execution during pipeline load, because the dataset calls torch.load on .pt files without enforcing weights_only=True and silently drops user-supplied load_args, so even an explicit weights_only override never reached PyTorch. Exploitation requires a PyTorch runtime earlier than 2.6 (where weights_only defaults to False) plus a victim pipeline that loads a checkpoint obtained from an attacker-influenced shared model registry, downloaded checkpoint, or partitioned external dataset; unauthenticated remote attackers can plant the payload but must wait for that user interaction, and pipelines loading only trusted files are unaffected. There is no public exploit identified at time of analysis and no confirmed active exploitation; the vendor-released patch is version 9.5.0, which enforces weights_only=True by default and correctly forwards load_args and save_args.
Arbitrary file write via path traversal in ComfyUI before 0.30.0 lets an attacker place attacker-controlled content anywhere on the host filesystem by supplying a crafted folder_name to the dataset save nodes. According to the vendor vector, no authentication is required (PR:N), but exploitation requires user interaction in the form of the victim loading and running a malicious workflow (UI:P); code execution does not occur immediately and instead follows when the written startup file or package initializer is subsequently loaded. Publicly available exploit code exists (a published PoC walkthrough and a VulnCheck advisory), the affected versions are in default configurations, and the vendor has released a fix in 0.30.0; there is no indication of confirmed active exploitation (CISA KEV), and this is not an unauthenticated remote worm-class flaw despite its 8.5 severity, because the local vector and mandatory workflow-import step constrain delivery.
Refine's @refinedev/inferencer package through version 7.0.0 interpolates API field names straight into generated JSX source without escaping, so an attacker who controls or has compromised the data provider can supply crafted JSON property names that execute as JavaScript in a developer's browser when an Inferencer-generated page renders. Remote, unauthenticated input is possible per the published vector (PR:N), but exploitation is gated on developer interaction (UI:P/UI:R), a malicious or untrusted backend (AC:H/AT:P), and a developer actually previewing Inferencer output - hence our independent assessment rates real-world risk materially below the 7.7 CVSS 4.0 headline, and no public exploit code was identified at time of analysis. The issue is tracked upstream in the refinedev/refine repository as issue #7556.
BC Security Empire before 6.7.1 is affected by an authenticated path traversal vulnerability in its multipart file upload flow; an operator with a valid Empire session can place a traversal sequence in the uploaded filename and write files outside the intended downloads directory on the C2 server, potentially achieving code execution. The issue is fixed in 6.7.1, which validates filenames and resolves upload paths safely; no public exploit identified at time of analysis, and CVSS 4.0 rates it 8.7 (assessed CVSS 3.1 8.8) with high confidentiality, integrity, and availability impact. Exploitation requires network access to the C2 REST API and valid credentials or a hijacked operator session, so patched or access-restricted deployments are not exposed.
HP Advance server software contains a path traversal vulnerability (CWE-22) in its HP AC Print & Scan and HP Output Central components, allowing unauthenticated remote attackers to write arbitrary files, which can lead to remote code execution or privilege escalation. The vendor CVSS 4.0 vector (8.8) rates it network-reachable and unauthenticated with high integrity and availability impact, but HP notes impact occurs 'under certain conditions,' implying unstated deployment prerequisites that may narrow actual exploitability; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated remote code injection in HP Advance can let an attacker with network reachability to the print-management server hosting HP AC Print & Scan or HP Output Central achieve elevation of privilege, remote code execution, or arbitrary file write, as described in HP's self-published advisory hpsbpi04149 (CVSS 4.0 base score 9.3 Critical, CWE-94). The vendor scores both the vulnerable component (VC:H/VI:L) and subsequent systems (SC:H/SI:H) as impacted, and our independent assessment retains a high-severity rating (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) while noting that HP's explicit 'under certain conditions' wording implies a specific feature, endpoint, or deployment mode is a likely precondition despite the AC:L rating. Exploitation requires no authentication and no user interaction per the CVSS vector, but there is no CISA KEV entry, no public exploit code identified at time of analysis, and no affected version range published by the vendor.
Unauthenticated remote code execution and privilege escalation in HP Advance software can lead to full server compromise, but exploitation requires specific, undisclosed configuration or deployment conditions according to HP's advisory. The flaw affects the HP AC Print & Scan and HP Output Central components hosted on the HP Advance server. No public exploit code has been identified at time of analysis, though the vendor's CVSS 4.0 vector rates it 9.3 critical while an independent assessment adjusts attack complexity to High due to the gating conditions.
Arbitrary code execution in Redocly CLI and @redocly/respect-core before version 2.33.0 allows a crafted Arazzo description to run attacker-controlled JavaScript with the privileges of the CLI process. The flaw lives in the `respect` command's `$faker` runtime-expression evaluator (get-value-from-context.ts), which permits property traversal through `constructor`, `prototype`, and `__proto__` to reach the JavaScript Function constructor; because the vector is local (AV:L) with required user interaction (UI:R, PR:N), a victim or CI job must actually process an untrusted, attacker-supplied workflow description for exploitation to occur. Impact is high in CI environments, where the injected code can execute shell commands or read pipeline secrets, while users who only run trusted, self-authored workflows are unaffected; no public exploit code was identified at the time of analysis, but a patch exists in 2.33.0.
Heap-based buffer overflow (CWE-122) in HP's HPLIP - the HP Linux Imaging and Printing Software stack shipped as the default printer/scanner driver on most Linux distributions - can be triggered when attacker-influenced data is processed by a vulnerable component, potentially leading to remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. This is a bundled advisory covering multiple externally reported flaws across several HPLIP components, so the precise prerequisites vary per sub-vulnerability; the vendor assigns CVSS 4.0 score 9.3 (Critical) with a remote, unauthenticated, low-complexity vector, while the independent assessment is more conservative at CVSS 3.1 AV:N/AC:H/PR:N/UI:N, reflecting that the system must be running HPLIP and actually process malicious input. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary code execution in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled allows an unauthenticated gNPSI client to craft a malicious request that executes code on the switch, yielding full administrative control of the device. The exploit path is gated by a hard precondition: gNPSI is not enabled by default and the gRPC endpoint must be network-reachable, which the vendor vector captures as AT:P and the advisory describes as 'under certain circumstances'; given that condition, no authentication (PR:N) or user interaction (UI:N) is needed. The vulnerability is rated critical (CVSS 4.0 base 9.2, independent 3.1 assessment AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact), and no public exploit code has been identified at time of analysis, so realistic risk is concentrated on switches where gNPSI has been turned on and exposed to untrusted network segments.
HPLIP (HP Linux Imaging and Printing Software) is affected by multiple heap-based buffer overflow vulnerabilities (CWE-122) that can lead to remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. Exploitation requires user interaction, such as a victim performing a print or scan operation or processing attacker-supplied imaging data, but no authentication is needed, and the attack is network-reachable. HP has remediated the issues; no public exploit code has been identified at the time of analysis.
Heap-based buffer overflow and related memory-safety flaws in HP Linux Imaging and Printing (HPLIP) can allow remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification on Linux hosts where HPLIP is installed and the affected component is active. This is an aggregate HP bulletin (hpsbpi04151) that bundles multiple externally reported issues under one CVE, so the published CVSS 4.0 score of 9.3 (AV:N/AC:L/PR:N/UI:N/VC:H/VI:H/VA:H) represents the worst-case component rather than any single flaw, and the assessed CVSS 3.1 score is lower (AV:N/AC:H) because several sub-issues are more likely local than remote and heap exploitation requires reliable memory grooming. No public exploit code or confirmed active exploitation was identified at time of analysis, and the exposure is limited to Linux systems on which HPLIP is deployed rather than being a universal service.
Command injection weaknesses in HP Linux Imaging and Printing Software (HPLIP) allow a local attacker to execute arbitrary operating-system commands with the privileges of the affected HPLIP component, resulting in high confidentiality, integrity, and availability impact (vendor CVSS 4.0 base 8.4) and spanning remote code execution, privilege escalation, denial of service, information disclosure, and unauthorized file modification. Exploitation is not remote: it requires local access to a Linux host that has HPLIP installed and in use, and it requires active user interaction, typically by inducing a legitimate user to feed attacker-controlled input into a vulnerable HPLIP component that builds an OS command (CWE-78). No authentication or elevated privileges are needed (PR:N), and no public exploit code or confirmed active exploitation was identified at time of analysis; HP has released remediation for the affected components in advisory HPSBPI04151.
Heap-based buffer overflows and related memory-safety flaws in HPLIP (HP Linux Imaging and Printing Software) let remote attackers corrupt memory in the print, scan, and device-discovery stack, potentially yielding remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. Only Linux hosts with HPLIP installed and actively processing attacker-influenced input - a crafted print job, a rogue printer/scanner response, or a file handled by the HPLIP stack - are affected, and exploitation is gated on active user interaction (initiating or accepting the malicious print/scan operation) rather than being a fully autonomous remote exploit. The flaws are unauthenticated per the vendor CVSS vector (PR:N), impact varies depending on which bundled sub-vulnerability is triggered, and no public exploit identified at time of analysis.
Out-of-bounds write flaws in HPLIP (HP Linux Imaging and Printing Software) can corrupt memory when a user processes attacker-influenced input such as a crafted print job, a malicious device or network response, or a handled file, with the affected product confirmed by HP and documented in advisory HPSBPI04151. No authentication is required to reach the vulnerable components, but exploitation depends on mandatory user interaction and on hosts that actually have HPLIP installed and in active printing or scanning use. Worst-case impact spans remote code execution, privilege escalation, denial of service, information disclosure, and unauthorized file modification; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated remote code execution in Cisco ISE allows an attacker with low-privileged administrative credentials to execute arbitrary commands on the underlying operating system and elevate to root via insecure deserialization of a crafted Java object sent to the web-based management interface. Exploitation requires network access to the management interface and valid low-privileged admin credentials (CVSS 9.9, PR:L), and successful attacks on single-node deployments can cause a denial-of-service condition that prevents unauthenticated endpoints from accessing the network. No public exploit has been identified at time of analysis.
Command injection in the REST API of Cisco ISE and ISE-PIC allows authenticated administrators to execute arbitrary commands with root privileges on the underlying operating system, potentially leading to complete node compromise and, in single-node deployments, a denial-of-service condition. This vulnerability (CVE-2026-20306) requires valid administrative credentials (PR:H) and network access to the management interface; no public exploit code has been identified at the time of analysis. The CVSS 3.1 base score is 9.1, driven by the high impact of root-level code execution and scope change from the web application to the OS.
Cisco ISE and ISE-PIC contain an OS command injection flaw (CWE-78) in their web-based diagnostic tools that lets an authenticated remote attacker with valid administrative credentials execute arbitrary commands and gain root on the underlying operating system. Because the attacker must already hold admin rights (PR:H), this is primarily a privilege-escalation and integrity-risk issue rather than an anonymous entry point, though the CVSS 3.1 score is 9.1 Critical (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) due to the scope change and full loss of confidentiality, integrity, and availability. On single-node deployments, successful exploitation can render the ISE node unavailable and block endpoints that have not yet authenticated from reaching the network, producing a denial-of-service condition; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Path traversal and arbitrary file write in the oras-go OCI artifact library prior to 2.6.2 allow a malicious artifact layer marked with the io.deis.oras.content.unpack=true annotation to escape the content/file.Store extraction root and create or overwrite any file writable by the pulling process, potentially leading to code execution. Exploitation is unauthenticated from an attacker's network position (CVSS:3.1/AV:N/AC:L/PR:N) but requires user interaction (UI:R) because the victim must pull the attacker-controlled artifact reference; the bug bypasses the AllowPathTraversalOnWrite=false default, so no permissive configuration is needed. Scored 8.8 High, with no public exploit identified at time of analysis and no CISA KEV listing; a vendor patch is available in oras-go 2.6.2.
Stack-based buffer overflow in the Dell Update Package (DUP) Framework, affecting versions prior to 26.07.03, allows an unauthenticated attacker on the same local network segment (AV:A) to corrupt stack memory and achieve arbitrary code execution on the affected host with full confidentiality, integrity, and availability impact. Exploitation requires no credentials or user interaction and is low-complexity once the attacker has L2 adjacency to a system running the vulnerable framework, though it is not reachable from the internet and CISA SSVC rates it non-automatable with only partial technical impact. No public exploit code has been identified at time of analysis and EPSS is low (0.30%, 22nd percentile); Dell has released a fixed version.
Zip-slip path traversal in the Stanford NLP Stanza Python library before 1.14.0 lets a malicious model or resource archive write files outside the intended model directory, overwriting anything writable by the Stanza process and potentially achieving code execution via modified shell configuration, SSH authorized_keys, Python packages, or executable scripts. The vulnerable code path is reached when a victim runs stanza.download() or stanza.install_corenlp(); exploitation therefore requires the fetched archive to be attacker-controlled (compromised or malicious mirror, MITM of the transfer, or a victim-supplied resource URL) plus user interaction to initiate the download. Rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and tracked as CWE-22; unauthenticated per the PR:N vector but local and interaction-dependent, with no public exploit identified at time of analysis and a vendor patch available in 1.14.0.
Remote code execution in InternLM LMDeploy versions 0.9.1 through 0.10.1 allows unauthenticated network attackers to run arbitrary commands by sending crafted pickle payloads to the AsyncRPCServer RPC endpoint (zmq_rpc.py). The service deserializes raw messages with pickle.loads() and performs no authentication or IP validation, so any attacker who can reach the randomized port-typically found by scanning-can trigger code execution; publicly available exploit code exists (proof-of-concept with reverse shell demo), and the CVSS 3.1 score is 9.8. This is not confirmed actively exploited (no CISA KEV listing), and exploitation is not possible if the RPC service is bound exclusively to localhost; upgrading to 0.10.2 patches the deserialization flaw and restricts the RPC to localhost.
Authenticated remote code execution in ScadaLTS 2.8.1-release-candidate build 0 allows any holder of a low-privilege account to run arbitrary JavaScript on the server by abusing the scripting sandbox. The DWR-exposed DataSourceEditDwr.validateScript method performs no authorization check and is reachable through a DWR routing bypass, so supplied code is compiled and executed by the Rhino engine with the application's privileges (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status; the independent assessment treats this as a genuine, credible priority rather than an inflated high-CVSS artifact, with the requirement for valid credentials being the principal limiting factor.
Authenticated users who can register or modify a TechDocs documentation source can achieve code execution inside the Backstage TechDocs backend or its build container by supplying a crafted mkdocs.yml, because @backstage/plugin-techdocs-node fails to strip unsafe Python YAML tags, markdown_extensions names and their configuration, theme options, and extra_templates values before the file reaches the Python documentation generator. The flaw affects the techdocs-node plugin before 1.14.6 and the 1.15.0 through 1.15.3 range, and the vendor has released fixes in 1.14.6 and 1.15.4. Authentication is mandatory per the CVSS vector (PR:L), no public exploit code or confirmed active exploitation was identified at time of analysis, and the blast radius is limited to the files, credentials, and network reach of the TechDocs backend or build container rather than the wider Backstage host.
Sandbox escape in RestrictedPython versions prior to 8.4 lets code executing inside the restricted context reach host-level primitives - function globals, builtins, file access, and code-execution gadgets - whenever the host exposes the standard-library string module, the string.Formatter class, a Formatter instance, or a Formatter subclass to that restricted code. The prerequisite is non-default: stock RestrictedPython does not surface these objects, so a custom import policy or specially crafted globals must be in place, and the attacker must also be able to submit restricted Python code (typically an authenticated user of the hosting application). A vendor patch is available in 8.4; no public exploit was identified at time of analysis.
Path traversal in the Jenkins Robot Framework Plugin (6.2.2 and earlier) allows an authenticated user holding Item/Configure permission to point the plugin's report archive directory at a location outside the build directory, giving attacker-chosen file creation or overwrite anywhere on the Jenkins controller filesystem - an impact that can be escalated to remote code execution. The flaw is remotely reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) and requires no user interaction, but it is gated by the Item/Configure privilege, plugin installation and use, and a build actually executing to trigger the write. No public exploit code has been identified at time of analysis, and the risk concentrates on multi-user or multi-tenant controllers where lower-trust users are permitted to configure jobs.
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets an authenticated attacker who holds permission to define classpath entries run attacker-supplied code inside the Jenkins controller JVM. The plugin downloads the URL-specified JAR twice - it verifies approval against the first response but then loads classpath entries from the second - so an attacker who controls the hosting server can present a benign, approvable JAR on request one and a malicious JAR on request two. The assessed CVSS 3.1 vector (7.5, AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects this time-of-check/time-of-use race: the flaw is remotely reachable but requires an authenticated classpath-defining user and a reliably won race; there is no public exploit code and no confirmed active exploitation identified at time of analysis.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-configure privileges defines classpath entries in an item configuration, those entries are silently auto-approved the moment a user holding Overall/Administer permission copies that item or updates its configuration through the REST API or CLI. The result is code execution inside the Jenkins controller JVM (CWE-94, CVSS 8.0), but exploitation is a two-actor, confused-deputy scenario: the attacker needs pre-existing config-edit rights (PR:L) and must wait for a privileged user to perform the copy or API/CLI update (UI:R), so installations where only administrators author jobs and never copy them or drive configuration through REST/CLI are effectively unexposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows an authenticated Jenkins user who holds permission to define and run sandboxed scripts - including Pipelines - to execute code outside the Groovy sandbox by supplying an @Builder annotation whose builderStrategy member names an arbitrary class. Exploitation additionally requires that a suitable "gadget" class be present on the classpath of the component that evaluates the script, which is why the assessment rates it AC:H despite high C:H/I:H/A:H impact and a scope change (S:C) across the sandbox boundary; the limitation is that only instances where untrusted or low-privilege users can author sandboxed scripts are meaningfully exposed. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; EPSS is 0.20% (11th percentile), consistent with a high-severity but precondition-heavy flaw rather than a mass-exploitable internet threat.
Sandbox escape leading to arbitrary code execution inside the Jenkins controller JVM affects Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier because the plugin fails to reject the @GroovyASTTransformationClass annotation in script source. An authenticated Jenkins user with permission to define and run sandboxed scripts, including Pipelines (the CVSS vector carries PR:L), can submit a script that registers a Groovy AST transformation executed at compile time, before the sandbox applies, resulting in high confidentiality, integrity, and availability impact on the controller; our independent assessment scores this 8.8 with a scope change (S:C) rather than the provider's S:U. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but for any account holding script-submission rights the exploit path is direct rather than theoretical, so the practical risk concentrates on instances that grant Job/Configure or equivalent Pipeline-authoring rights broadly. This is a genuine high-priority vulnerability, not CVSS inflation: the sandbox itself, not a misconfiguration, is the control being bypassed.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated attacker with permission to define and run sandboxed Groovy scripts or Pipelines to bypass the sandbox and run code in the Jenkins controller JVM. The flaw is a protection mechanism failure (CWE-693) in how the plugin casts collections, and it carries CVSS 8.8 with PR:L; only users who can author sandboxed scripts or Pipelines can trigger it. No public exploit code was identified at time of analysis, and CISA SSVC rates exploitation as none, but this is high-priority for multi-tenant Jenkins because script-authoring rights are often broadly granted.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows authenticated users with permission to define and run sandboxed Groovy or Pipeline scripts to execute arbitrary code in the Jenkins controller JVM, because the sandbox fails to intercept method calls, property and attribute accesses, and array accesses made on a null receiver. No non-default configuration is required - the weakness is inherent to the default sandbox - and the flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-693), with CISA SSVC assessing total technical impact but no active exploitation and no public exploit identified at time of analysis. Real-world urgency is moderated by the access prerequisite: the attacker must already hold script-authoring rights, so exposure is concentrated in multi-tenant or delegated Jenkins instances where Pipeline authoring is granted to less-trusted users.
Sandbox escape in the Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier lets an authenticated user who holds permission to define and run sandboxed scripts - including Pipelines - execute arbitrary code in the Jenkins controller JVM, earning a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a protection-mechanism failure (CWE-693): the sandbox proxy created when a script coerces a value to a Java interface skips the method check when the coerced value inherits a same-named method, so the interface proxy can be used to reach unchecked code. No public exploit code has been identified at time of analysis and CISA SSVC rates the issue non-automatable (Exploitation: none, Automatable: no, Technical Impact: total), so mass exploitation is not expected; the binding prerequisite is the authenticated script-authoring permission reflected by PR:L, which makes this a real but privilege-gated RCE-class risk.
Unauthenticated remote code execution affects Check Point Quantum Security Management, where a stack-based buffer overflow is reachable through the login process before authentication completes. Because the flaw is triggered during the pre-authentication login path, a remote attacker with network reachability to the management server's login/administration service needs no credentials, no user interaction, and no non-default configuration, and the resulting code execution is described as running with root privileges - consistent with the CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV), but the pre-auth, root-level impact and the criticality of the management plane make this a top-priority patch target; CPE data lists the product with a wildcard version, indicating the affected version range is not bounded in the available feed data.
Arbitrary Lua code execution is possible on Advantech EKI-1242EIMS and EKI-1242IEIMS industrial Modbus gateways running firmware V1.06.01, because the Modbus CSV import workflow fails to neutralize code embedded in an uploaded configuration file (CWE-94). Exploitation requires an attacker to already hold a high-privilege authenticated session on the device web management interface and to be able to reach that interface over the network, which materially limits exposure in properly segmented OT environments; no user interaction on the part of a legitimate operator is needed, only the attacker's own crafted upload. Successful exploitation yields full loss of confidentiality, integrity, and availability of the device, but no public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (not listed in CISA KEV); the vulnerability was identified by Nozomi Networks Labs and a vendor security advisory has been published.
Code injection in the web management interface of Advantech EKI-1242IEIMS (and the closely related EKI-1242EIMS) industrial gateways on firmware V1.06.01 lets a remote attacker who already holds high-privilege web UI credentials execute arbitrary code on the device, including OS commands running as root. Exploitation is low-complexity once the attacker is authenticated, but the admin credential requirement (CVSS PR:H) is a hard gate that limits exposure to devices whose management interfaces are reachable and whose admin accounts have been compromised, reused, or left at weak/default values. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing); Advantech has published a security advisory for the issue, with Nozomi Networks Labs credited for the discovery. Risk framing: this is a genuine but access-gated risk concentrated on internet- or flat-network-exposed management interfaces rather than on segmented OT deployments.
Unauthenticated remote code execution affects Arista EOS platforms on which the non-default P4Runtime service has been explicitly enabled, letting an attacker who can reach that service take complete administrative control of the switch. The defect is a code-injection flaw (CWE-94) triggered by a crafted packet during P4Runtime session initiation, rated 9.5 Critical under CVSS 4.0 and assessed as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with high attack complexity and a changed scope because compromise of the switching platform can extend to subsequent systems. Exposure is limited: P4Runtime is disabled by default, so stock EOS deployments are not at risk, and successful exploitation also depends on a specific timing/condition requirement (AT:P, 'Attack Requirements: Present'); Arista discovered the issue internally, reports no malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis.
Authenticated remote code execution in Arista EOS allows a malicious client with valid gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch by sending a single specially crafted request. Only switches where gNMI has been explicitly enabled are exposed - gNMI is a non-default management API - and the attacker must already hold working gNMI credentials, which limits practical exposure to insiders or adversaries who have already compromised network-automation or management accounts, but grants them full root control of the device with low attack complexity and no user interaction. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); no EPSS score was provided. The vendor has published security advisory SA-0166 at https://www.arista.com/en/support/advisories-notices/security-advisory/24722-security-advisory-0166.
Heap-based memory corruption in NLnet Labs Unbound up to and including 1.26.0 lets a remote, unauthenticated attacker who controls or spoofs the upstream DNS response (PR:N/UI:N) gradually overwrite heap memory, with the reliable outcome being a crash and remote code execution possible only on certain systems and compilation options that lack hardening. The flaw is scored CVSS 8.4 (CVSS:4.0) and by the independent assessment as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with the high attack complexity reflecting heavy dependence on heap layout and non-deterministic results. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no KEV listing or EPSS signal is present, so this is a genuine but not-yet-urgent priority for internet-facing recursive resolvers.
A crafted DNSKEY whose owner name is a compression pointer into its own RDATA overflows the digest buffer in the DNSSEC validator of NLnet Labs Unbound 1.26.0 and earlier, letting an attacker who controls an authoritative zone crash a validating recursive resolver and, depending on heap layout, potentially execute code with attacker-influenced data. Exploitation is unauthenticated over the network per the CVSS vectors but is gated on DNSSEC validation being active and on inducing the resolver to query a name in the attacker's zone; the independently assessed impact is primarily denial of service (availability High, confidentiality and integrity Low), with remote code execution only possible rather than demonstrated. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, although the vendor rates the issue 9.1 under CVSS 4.0 and an advisory has been published.
Remote code execution is achievable on Pepperl+Fuchs ICE2/ICE3-series IO-Link Master devices and the Phoenix Contact IOL MA8 via a local file inclusion flaw in the `/index.php/ajax/save_iodd_parameters` AJAX endpoint. An authenticated attacker holding a valid operator-level session cookie can supply a crafted filename parameter that causes the PHP runtime to include and execute an attacker-controlled file, yielding full device compromise. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation requires prior acquisition of operator credentials.
Remote code execution via PHP local file inclusion on Pepperl+Fuchs ICE2/ICE3 series IO-Link Master devices and OEM equivalents (Phoenix Contact, Indu-Sol variants) allows a low-privileged authenticated attacker to execute arbitrary PHP code by supplying a crafted parameter to the /index.php/ajax/get_iodd_port_info endpoint. The vulnerability requires only a valid user session cookie, making it accessible to any account holder on these industrial automation gateways. Three separate CERT VDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the same vulnerable firmware is shipped under at least three different vendor brands, broadening the affected fleet across OT environments. No public exploit code or active exploitation has been identified at time of analysis.
Path traversal in Octopus Server allows an authenticated low-privilege user to overwrite arbitrary files on the server filesystem, which in certain configurations escalates to remote code execution. Affected are three distinct release trains of Octopus Server (CPE: cpe:2.3:a:octopus_deploy:octopus_server). No public exploit or CISA KEV listing exists at time of analysis, and a vendor patch is available across all three affected version ranges.
Arbitrary file upload with remote code execution impact in the WordPress plugin WP Import Export Lite affects every version before 3.9.33, allowing an authenticated user who holds the plugin's import permission to make the server fetch a remote file of the attacker's choosing and store it without any validation of type, extension, or content. The plugin's URL-based import path performs no content checks, so executable files can be planted on the host and executed; the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) confirms the low-privileged-but-authenticated prerequisite and no victim interaction. Publicly available exploit code exists, though EPSS is currently low at 0.25% (17th percentile), reflecting the limited population of sites that both run the plugin and expose the import capability; a vendor fix is available in 3.9.33. This is a genuine priority for any site running WP Import Export Lite before 3.9.33, tempered by an authentication prerequisite.
Unrestricted PHP function invocation in the WP Import Export Lite WordPress plugin before 3.9.33 allows a user holding the plugin's export permission to achieve remote code execution by applying arbitrary PHP functions to exported field values they control. Exploitation requires an authenticated, high-privilege account (PR:H in the assessed CVSS vector) that can configure and run an export, needs no user interaction, and is network-reachable. Publicly available exploit code exists, though EPSS is low at 0.27% (20th percentile) and there is no CISA KEV listing; the vendor has released a fix in version 3.9.33.
Remote code execution in the WP Import Export Lite WordPress plugin before 3.9.34 requires an authenticated user who has been granted the plugin's export permission, a privileged, non-default capability typically held by administrators or trusted operators. The plugin does not validate the user-supplied output path or filename when its export routine writes files, so that user can write a file with an arbitrary name - for example a .php webshell - into an arbitrary web-accessible directory and have it executed with the web server's privileges. Publicly available exploit code exists, but the flaw is not listed in CISA KEV, there is no confirmed active exploitation, and EPSS is low at 0.27% (20th percentile); the vendor has released 3.9.34 as the fix.
Arbitrary file overwrite in the Contest Gallery WordPress plugin (Upload & Vote Photos, Media, Sell with PayPal & Stripe) affects all versions up to and including 32.0.1, where the 'baseUrlForFacebook' parameter is passed to a file-writing routine without adequate path validation. Exploitation requires at least a subscriber-level account on the target WordPress site, but then allows overwriting known files on the server, which can escalate to remote code execution when the overwritten path is a PHP file that the web server later executes. No public exploit code or CISA KEV listing was provided in the source data for this CVE, so active exploitation is unconfirmed at time of analysis.
Local privilege-abuse code execution affects Howyar Technologies' SysReturn disk-protection solution in all versions prior to 11.3.034 (fixed in v11.3.0.34): a privileged local attacker who can write to the EFI System Partition can drop the SysReturn UEFI loader (BOOTia32.efi) alongside a crafted cloak32.dat data file, which the trusted boot-time component parses and executes code from at the next boot. Exploitation requires ESP write access - admin/root on a running system, or physical/offline access to the machine or its boot media - so this is a local vector (AV:L) with PR:H per the assessed vector, not a remote or unauthenticated path; CISA KEV does not list active exploitation, though public exploit code is referenced via the linked GitHub researcher repositories. Practical risk is concentrated on SysReturn-protected endpoints such as kiosks, shared lab PCs, and locked-down workstations where an insider or a prior compromise can modify the ESP and then achieve boot-time code execution with high confidentiality, integrity, and availability impact.
Arbitrary code execution in Sogou Input Method versions before 16.3.0.3498 allows a remote attacker to run code through the biz_helper.exe helper component on Windows. The vendor CVSS vector is AV:N/AC:L/PR:N/UI:N (9.8), but the independent assessment rates the vector as AV:N/AC:L/PR:N/UI:R, meaning a victim likely must interact with attacker-controlled content for exploitation. No public exploit identified at time of analysis, and upgrading to 16.3.0.3498 or later is the confirmed fix.
Heap-based buffer overflow in GIMP's file-psd import plugin allows a crafted PSD file to corrupt adjacent heap memory, causing an application crash or potentially arbitrary code execution when the user opens the file or when a thumbnail preview is generated for it. The root cause is an integer overflow (CWE-190) in the multiplication of values taken from an embedded JPEG header, which yields an undersized heap allocation that is subsequently overrun during image decoding and can be turned into a controlled memory write. The assessed vector (CVSS 3.1, 7.8 High, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms this is a local, user-interaction-dependent flaw rather than a remotely reachable service bug, so exploitation requires delivering the malicious PSD to a machine where GIMP or an automatic PSD thumbnailer processes it; no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV.
Remote compromise of Oracle GraalVM is possible: an unauthenticated attacker with HTTP access can exploit a defect in the Compiler component to achieve full takeover of the affected runtime, with high confidentiality, integrity and availability impact. Affected builds are Oracle GraalVM for JDK 17 (23.0.13.1), Oracle GraalVM for JDK 21 (23.1.12.1) and Oracle GraalVM 25 (25.0.4.1). No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, so exploitation is currently assessed as targeted rather than opportunistic; note that the accompanying 'Information Disclosure' tag understates the stated impact.
A stack-based buffer overflow in the Netcore NR255-V router (firmware 1.5.130703) allows an attacker who can reach the web management interface to smash a fixed-size stack buffer by submitting oversized form values to the ntools_tcpdump_start_set.cgi endpoint, which passes input to an unsized sprintf call. Successful exploitation can corrupt the saved return address and potentially lead to arbitrary code execution with the privileges of the CGI process on the device. The supplied CVSS 4.0 vector (8.7) rates confidentiality, integrity and availability impact as high with a network vector, but PR:L indicates some level of authentication or low-privilege access is required; no EPSS score, CISA KEV listing, or confirmed public exploit code was included in the intelligence feed, and no vendor patch reference was provided.
PHP object injection in the Cotonti 1.0.0 Comments plugin allows unauthenticated, network-reachable attackers to instantiate arbitrary PHP classes with attacker-controlled properties by feeding a crafted base64-encoded payload through the `ci` GET parameter, which is passed to unserialize() without an allowed_classes restriction. Any default Cotonti 1.0.0 deployment with the Comments plugin enabled and its widget rendering is exposed; no credentials or user interaction are required, and successful gadget-chain abuse can lead to database manipulation or remote code execution. No public exploit code was identified at time of analysis, and there is no confirmed active exploitation (CISA KEV), though the vendor has published an upstream fix via pull request #1889 that hardens the deserialization call.
Use-after-free in the Workers component of Google Chrome allows an unauthenticated remote attacker to execute arbitrary code outside the browser sandbox when a victim renders a crafted HTML page in any build prior to 153.0.8010.47, including default desktop installations on Windows, macOS and Linux. The only prerequisite is user interaction - opening or being lured to the malicious page (UI:R) - with no special configuration or prior access needed, and because the flaw yields a scope change the compromise extends to the host rather than remaining confined to the renderer. Google rates the issue Critical and has shipped a fixed build; exploitation is not currently observed, CISA's SSVC assessment classifies the flaw as not automatable, and no public exploit identified at time of analysis, though the combination of network reachability, low attack complexity and total technical impact makes it a genuine high-priority vulnerability for prompt patching.
A time-of-check-to-time-of-use race condition in the Extensions component of Google Chrome on macOS allows an attacker to break out of the renderer sandbox and execute arbitrary code in the browser process context. The barrier to entry is meaningful: the attacker must already have compromised the renderer process through a separate bug and then use social engineering to persuade the victim into a specific UI interaction that widens the race window. Affected builds are Chrome for macOS prior to 153.0.8010.47, and Google rates the issue High severity; no public exploit code or CISA KEV entry was identified at time of analysis.
Use-after-free in the V8 JavaScript engine of Google Chrome desktop builds prior to 153.0.8010.47 allows unauthenticated remote attackers to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. Because the CVSS vector is PR:N/UI:R, no credentials or special browser configuration are required, but the victim must actively navigate to attacker-controlled content; the memory-corruption primitive is confined to the renderer process, so full host compromise would require a second, independent sandbox-escape vulnerability. No public exploit code has been identified at time of analysis, and the vendor has released a fixed build, making this a high-priority patch item rather than a confirmed active-exploitation emergency.
Sandbox escape in Google Chrome prior to 153.0.8010.47 allows a remote attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox via a race condition (TOCTOU) triggered by a crafted HTML page; the user must visit that page for the flaw to be reachable. Google rates the issue Chromium security severity High and a vendor patch is available from the 153.0.8010.47 stable channel release. There is no public exploit code and no CISA KEV listing at time of analysis, and the high attack complexity combined with a required renderer-compromise precondition keeps realistic risk below the raw 8.3 CVSS score.
Type confusion in Chrome's CacheStorage implementation in builds prior to 153.0.8010.47 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page. The bug is rated High by Chromium and 8.8 by NVD (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), but it is a renderer-level compromise rather than a sandbox escape, so host impact requires chaining a second vulnerability. No CISA KEV listing and no public exploit code were identified at time of analysis, and no EPSS score was supplied in the input data.
Improper input validation in ANGLE, Google Chrome's graphics abstraction layer, allows a remote attacker to potentially execute arbitrary code outside the browser sandbox by convincing a user to open a crafted HTML page in Chrome builds prior to 153.0.8010.47. Exploitation requires no authentication (PR:N) but does require user interaction (UI:R) - the victim must navigate to attacker-controlled or compromised content - and the scope-change metric (S:C) reflects that successful exploitation implies code execution escaping the renderer sandbox onto the host OS. The issue carries a Critical 9.6 CVSS rating and a vendor patch is available in Chrome 153.0.8010.47; there is no public exploit identified at time of analysis, and Chromium rates the underlying security severity as Medium.
Remote code execution inside the renderer sandbox can be triggered in unpatched Google Chrome builds by a use-after-free in the browser's built-in PDF rendering component. Exploitation is unauthenticated (CVSS PR:N) but requires the victim to open a crafted HTML page that embeds malicious PDF content (UI:R), and any resulting code execution is confined to Chrome's renderer sandbox - meaning this bug alone does not compromise the host and would typically need to be chained with a separate sandbox-escape flaw for full system compromise. A vendor patch is available in Chrome 153.0.8010.47; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the 8.8 CVSS score and the ubiquity of Chrome make timely patching a priority.
Use-after-free in Chrome's DOM implementation allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.47. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High by Chromium security severity; a vendor patch is available and no public exploit code or CISA KEV entry was identified at time of analysis.
Google Chrome versions earlier than 153.0.8010.47 contain an incorrect authorization flaw (CWE-863) in the WebUI subsystem that lets an attacker who already controls a compromised renderer process break out of the browser sandbox and run arbitrary code on the host via a crafted HTML page. Exploitation is a two-stage proposition: the attacker must first obtain renderer code execution, then chain this flaw to escape the sandbox, and the victim must load the malicious page. Google rates the Chromium security severity as High and has shipped a fix in Chrome 153.0.8010.47; no public exploit code or CISA KEV entry was identified in the available intelligence at time of analysis.
Incorrect authorization in Chrome's Core component on Windows (versions prior to 153.0.8010.47) lets a local attacker who can run a program on the machine break out of the browser sandbox and execute arbitrary code at the user's privilege level outside it. The flaw is rated High by the Chromium security team and carries CVSS 7.4 (AV:L/AC:H/PR:N/UI:N, C/I/A all High), reflecting a local-only but complete confidentiality, integrity and availability impact once the sandbox boundary is crossed. No public exploit code or CISA KEV listing was provided in the input, and Google has released a fixed stable-channel build, so this is best treated as a high-value chaining primitive rather than a currently mass-exploited issue.
Remote code execution inside the renderer sandbox affects Google Chrome desktop builds prior to 153.0.8010.47, caused by a type confusion flaw in the browser's compositing pipeline (CWE-843) that is reachable from a crafted HTML page. An attacker needs only to convince a user to load the page: the CVSS 3.1 vector is 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials or privileges are required, but user interaction is mandatory. Google rates the issue Chromium security severity High and has shipped a fixed stable-channel build; no public exploit code or CISA KEV listing appears in the supplied intelligence, and no EPSS score was provided, so the current exploitation picture is best described as patch-now-but-not-known-exploited.
Use-after-free in Google Chrome's DigitalCredentials component lets a remote, unauthenticated attacker execute arbitrary code outside the browser sandbox when a victim is socially engineered into loading a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47. Exploitation requires no credentials or elevated privileges (CVSS PR:N) but does require the user to navigate to the attacker-controlled page (UI:R), and the resulting scope change (S:C) means impact extends beyond the browser's sandbox boundary to full confidentiality, integrity, and availability loss. Google rates the issue High and has shipped a fix in the stable channel; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, so the current risk is driven by the ease of phishing/malvertising delivery rather than confirmed active exploitation.
Integer overflow in V8, Chrome's JavaScript engine, allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in Chrome builds prior to 153.0.8010.47; the bug carries a high CVSS (9.6 as published, scored 8.8 under our scope-unchanged reassessment) because memory corruption in V8 can be leveraged for code execution, though impact is confined to the renderer process and full host compromise would require chaining a separate sandbox-escape flaw. Chrome ships on a rapid auto-update cadence and a vendor patch is available (153.0.8010.47), which limits mass exposure; EPSS is a modest 0.36% (30th percentile), CISA SSVC records no observed exploitation, and no public exploit code has been identified at time of analysis, so this is a high-severity memory-safety defect to prioritize for unpatched or update-delayed enterprise fleets rather than an active-emergency. No authentication is required (PR:N), but exploitation depends on user interaction: the victim must load attacker-controlled JavaScript with scripting enabled in the default configuration.
Let me synthesize. CVE-2026-91727: Incorrect reference resolution in Extensions in Chrome on Mac prior to 153.0.8010.47. Local attacker who compromised renderer process could execute arbitrary code outside sandbox via a local program. CWE-706 (Use of Incorrectly-Resolved Name or Reference). CVSS 8.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Product: Google Chrome (macOS). Product name 1-3 words: "Google Chrome". Prevalence: ubiquitous. Now fields. Summary: must not copy description; start with impact verb and product. E.g. "Sandbox escape in Google Chrome on macOS (prior to 153.0.8010.47) lets an attacker who has already compromised the renderer process escalate to code execution outside the browser sandbox..." Technical context: CWE-706 incorrect reference resolution in Extensions — extension API resolves a reference (name/path/identifier) incorrectly, allowing a local program to be loaded/executed outside sandbox. macOS-specific. Renderer compromise prerequisite. Risk assessment: CVSS 8.1 with AV:L AC:H PR:N UI:N S:C. EPSS not provided, KEV not provided. Patch available. No POC known. Attack requires renderer compromise (two-stage). S:C indicates sandbox escape crossing security scope. Not KEV → no public exploit identified at time of analysis. Note missing EPSS/KEV data explicitly. Affected products: Google Chrome on macOS versions prior to 153.0.8010.47; EUVD lists "Chrome 153.0.8010.47 <153.0.8010.47" which is malformed/likely means before 153.0.8010.47. Reference: chromereleases blog, chromium issue 516893912. Remediation: upgrade to 153.0.8010.47 or later. Chrome auto-update. macOS-specific. Compensating controls: restrict extension installs via enterprise policy, disable extensions, etc. Trade-offs. Exploit scenario: attacker chains a renderer RCE (e.g. via malicious web content) then exploits the extension reference resolution flaw to break out of sandbox and run native code on macOS host. Exploitation conditions: requires (1) macOS platform, (2) att
Google Chrome builds prior to 153.0.8010.47 carry a use-after-free in the browser's Input component that allows an attacker who already controls a compromised renderer process to escape the Chrome sandbox and run arbitrary code with the browser's privileges. Exploitation is not remote-standalone: it requires a chained renderer compromise plus a victim who opens a crafted HTML page, which is why the flaw is scored High (8.3) rather than Critical despite total technical impact. Google has shipped a fixed stable-channel build; no public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis.
Use-after-free in Google Chrome's Input handling allows a remote attacker to achieve code execution in affected desktop builds prior to 153.0.8010.47. Exploitation is unauthenticated (PR:N) but requires the victim to render attacker-controlled HTML (UI:R), making drive-by or malicious-page delivery the primary vector; default configurations are affected with no non-default prerequisites. The vulnerability is rated CVSS 8.8 (C:H/I:H/A:H) and a vendor patch is available in the Stable channel build 153.0.8010.47; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
A use-after-free in Google Chrome's Internals component allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47 on desktop. Exploitation requires user interaction (visiting the page) but no authentication or elevated privileges, and Google rates the Chromium security severity as Critical. Vendor-released patch: 153.0.8010.47. There is no public exploit code identified at time of analysis and no confirmed actively exploited (CISA KEV) status, though the SSVC framework assigns total technical impact.
Code injection in XML handling in Google Chrome versions prior to 153.0.8010.47 could let a remote attacker bypass the web origin policy by luring a victim into opening a crafted HTML page (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N per independent assessment, versus Google's published 8.1 vector). Exploitation requires user interaction - the victim must load the malicious page - and no authentication is needed, while Google's own Chromium severity rating is 'Low', indicating constrained real-world impact; the EPSS score is 0.26% (17th percentile) and no public exploit has been identified at time of analysis. A vendor patch is available in Chrome 153.0.8010.47, and Chrome's automatic background update mechanism rapidly retires vulnerable versions.
Use-after-free in Google Chrome's Core component lets a remote attacker execute arbitrary code outside the browser sandbox by getting a victim to load a crafted HTML page in any build prior to 153.0.8010.47. The flaw is unauthenticated (PR:N) but requires user interaction (UI:R), and because the resulting code execution occurs outside the sandbox, Chrome's normal renderer isolation does not contain the compromise; the assessed severity is 9.6 with scope changed (S:C). No public exploit code has been identified at time of analysis, and a vendor-released patch is available in Chrome 153.0.8010.47.
Use-after-free in Google Chrome's Auth component allows a remote attacker to achieve code execution outside the browser sandbox when a victim simply loads a crafted HTML page in any desktop Chrome build prior to 153.0.8010.47. Exploitation is unauthenticated and requires no special configuration - the only prerequisite is the user interaction of visiting or rendering the attacker-controlled page (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6), and because the flaw is not confined to the renderer, no separate sandbox-escape bug is needed to reach the host. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Google has released a fixed build (153.0.8010.47), and details remain restricted in the Chromium tracker until most users have updated.
Type confusion in Chrome's ServiceWorker implementation allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by enticing a victim to load a crafted HTML page in any Chrome build prior to 153.0.8010.47. Exploitation is unauthenticated (PR:N) but requires user interaction (UI:R) - the victim must visit or be redirected to attacker-controlled content - and the resulting code execution is confined to the sandbox (S:U), so full host compromise would require chaining a separate sandbox-escape flaw. There is no public exploit identified at time of analysis, and a vendor-released patch (153.0.8010.47) is available, making this a high-priority but practically bounded patching task rather than an urgent zero-day response.
Google Chrome on macOS versions prior to 153.0.8010.47 contain a race condition (TOCTOU) in the Extensions subsystem that lets an attacker who has already compromised the browser's renderer process break out of the sandbox and execute arbitrary code on the host, triggered when a victim loads a crafted HTML page. Google rated the issue High severity and Chromium's own severity assessment drove the 8.3 CVSS base score with a Scope change (S:C), reflecting that code execution crosses the renderer/sandbox boundary rather than staying contained. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch is available and should be applied promptly because sandbox escapes are the high-value second stage of any Chrome exploit chain.
An out-of-bounds write in Google Chrome's ServiceWorker implementation allows remote code execution inside the browser's renderer sandbox when a victim loads a crafted HTML page; exploitation requires the user to visit or be redirected to attacker-controlled content and to have a service worker exercised (UI:R, PR:N), so no credentials or pre-existing privileges are needed. Successful exploitation yields high confidentiality, integrity and availability impact within the sandboxed renderer process (CVSS 3.1 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and host compromise would additionally require a separate sandbox-escape. Only Chrome builds prior to 153.0.8010.47 are affected, a vendor patch is available, and no public exploit code has been identified at time of analysis; because Chrome auto-updates in the background, most installations will remediate themselves quickly, though managed and long-lived sessions should be verified.
Use-after-free in Google Chrome's WebAppInstalls component allows a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim loads a crafted HTML page on any build prior to 153.0.8010.47. Exploitation requires user interaction (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6), and the scope-changed rating reflects that a successful attack escapes the renderer sandbox and reaches the host rather than staying contained in the browser process. At time of analysis there is no indication of active exploitation and no public exploit code identified; the vendor has shipped a fixed build (153.0.8010.47) and the primary exposure is unpatched consumer and enterprise Chrome installations.
Type confusion in Google Chrome's ServiceWorker implementation before version 153.0.8010.47 allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by getting a user to open a crafted HTML page. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R), the classic memory-corruption profile for Chrome renderer bugs, and Google rated it High in its Chromium severity scheme. A vendor patch shipped in the 153.0.8010.47 stable release, and there is no public exploit code identified and no CISA KEV entry at time of analysis, so this is a prioritise-and-patch issue rather than a confirmed active campaign.
Unauthenticated remote code execution in Tencent Mass Service Engine in Cluster (MSEC) lets a network-positioned attacker submit a crafted POST request containing ../ sequences to escape the intended upload directory, drop a webshell, and execute arbitrary commands with root privileges on the host. The exploitability signals are uniform: the vendor-assigned CVSS 4.0 base score of 9.3 with vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H describes a remote, low-complexity attack requiring no authentication and no user interaction, and our independent assessment (CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reaches the same conclusion. The practical limiting factor is deployment footprint rather than attack difficulty: MSEC is a niche open-source distributed backend framework, so real-world risk depends on whether a target actually runs MSEC and exposes its HTTP/upload request-handling service to the attacker's network; exploitation status is no public exploit identified at time of analysis (no CISA KEV entry and no published PoC in the supplied intelligence).
Authenticated attackers holding administrative access to the management plane of HPE Networking EdgeConnect SD-WAN Gateways can supply crafted input to an affected component and achieve arbitrary command execution as root. The flaw affects multiple released trains — 9.4.x up to 9.4.8.2, 9.5.x up to 9.5.8.1, 9.6.x up to 9.6.3.1, and 9.7.0.0 — with a CVSS base score of 7.2 reflecting the high privilege prerequisite against total loss of confidentiality, integrity, and availability. There is no CISA KEV entry, no EPSS score, and no public exploit code identified at time of analysis, so this is currently a high-impact but credential-gated risk rather than an actively exploited one.
Authenticated attackers who already hold administrative privileges on HPE Aruba EdgeConnect SD-WAN Gateways can supply specially crafted configuration data that overflows a stack buffer in the configuration processing logic, potentially yielding remote code execution as root or crashing the gateway into a denial of service. The flaw affects gateway releases in the 9.4.x (≤9.4.8.2), 9.5.x (≤9.5.8.1), 9.6.x (≤9.6.3.1) and 9.7.0.0 branches per the ENISA EUVD affected-version list, and carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). No public exploit code, CISA KEV listing or EPSS score was included in the supplied intelligence, so the observed exploitation status is unconfirmed at time of analysis.
Unauthenticated remote code execution and denial-of-service in HPE Aruba Networking EdgeConnect SD-WAN Gateways (versions 9.4.0.0–9.4.8.2, 9.5.0.0–9.5.8.1, 9.6.0.0–9.6.3.1, and 9.7.0.0) arise from flawed parsing of malformed or truncated packets in the proxy packet-processing path, where incorrect length arithmetic triggers an integer overflow that can become a memory-corruption (buffer overflow) condition. Successful exploitation can let a network-positioned attacker execute code or crash the gateway, taking down the SD-WAN overlay. The HPE advisory at support.hpe.com confirms affected version ranges, but there is no CISA KEV listing, no EPSS score, and no public exploit code identified at time of analysis, so this is currently a patch-now, watch-for-exploitation item rather than a confirmed active campaign.
A limited buffer overflow in the network security monitoring component of HPE EdgeConnect SD-WAN Gateways allows an unauthenticated remote attacker to crash the appliance and potentially execute code by driving crafted traffic into the monitoring parser. ENISA EUVD lists four affected release trains: 9.4.0.0 through 9.4.8.2, 9.5.0.0 through 9.5.8.1, 9.6.0.0 through 9.6.3.1, and 9.7.0.0. No CISA KEV entry and no public exploit code were identified at time of analysis, and no EPSS data was supplied with the record.
A buffer overflow in the underlying operating system of HPE Aruba Networking EdgeConnect SD-WAN Gateways lets an unauthenticated attacker on an adjacent network segment execute arbitrary code as a privileged OS user, resulting in full compromise of the appliance. Affected branches span the 9.4.x, 9.5.x, 9.6.x and 9.7.0.0 release trains (up to 9.4.8.2, 9.5.8.1, 9.6.3.1 and 9.7.0.0 respectively). The vendor describes exploitation as conditional on preconditions outside the attacker's control, and no public exploit code, EPSS score or CISA KEV entry was present in the supplied intelligence at time of analysis.
Local DLL search-order hijacking in the GeoVision GV-Remote E-Map Windows desktop application allows an attacker who already holds a local foothold with write access to a directory the application searches to execute arbitrary code in the security context of the GV-Remote E-Map process. The weakness is CWE-427 and is scored CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so it is not remotely exploitable and requires host-local write permission plus a normal application launch for the hijacked library to load. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, and the practical risk is largely determined by whether the application's install and working directories are ACL-restricted against standard users.
Opening an attacker-crafted Affinity document in Affinity by Canva versions prior to 3.3.0 can trigger a stack-based buffer overflow that may lead to arbitrary code execution on the victim's endpoint. Exploitation is not remote or automatic: it requires the user to open the malformed document (UI:R) on a machine where Affinity is installed, and attack complexity is assessed as high (AC:H), reflecting the difficulty of turning the stack corruption into reliable code execution in the presence of modern stack and memory protections. No confirmed active exploitation (CISA KEV) and no public exploit code have been identified at the time of analysis, and the risk is genuine but not top-tier - it is confined to endpoints that handle untrusted Affinity files.
Improper neutralization of newline sequences in NetworkManager-fortisslvpn credential handling allows a local user who can create or modify a FortiSSL VPN connection profile to inject directives that the root-privileged VPN helper executes, resulting in local privilege escalation to root. The flaw is scored 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and was reported by Ubuntu, with Red Hat tracking it through its CVE page and Bugzilla 2533640 against an upstream tracking item in the archived GNOME GitLab project. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so risk is concentrated on multi-user Linux hosts where the plugin is installed and ordinary console users are permitted by policy to configure VPN connections.
Server-side template injection in Craft CMS 5.10.0 through 5.10.12 allows an authenticated low-privilege control-panel user with edit rights on even a single element type to execute arbitrary PHP code and fully compromise the server. The bug is an incomplete fix for CVE-2026-55794: the Controller::getPostedRedirectUrl() to View::renderObjectTemplate() redirect sink stayed unsandboxed, and the same patch introduced a self-signing oracle in Cp::elementLabelHtml(); because Craft/Yii HMAC tokens are not bound to a parameter name, a token minted over attacker-controlled Twig for returnUrl can be replayed as the redirect POST parameter. Exploitation requires a valid CP account with element-edit permissions (PR:L, no user interaction); no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor-released patch is Craft CMS 5.10.13.
Code injection into the quay-builder-qemu release workflow through supply-chain compromise of the third-party GitHub Action `Noelware/docker-manifest-action`, which the workflow references by a mutable branch instead of a pinned immutable commit SHA. An attacker who first subverts that upstream action can execute arbitrary code inside the release pipeline, exfiltrating sensitive registry credentials or publishing malicious container images, with severity amplified because the workflow also exposes the default GITHUB_TOKEN. This is a CI/CD build-pipeline flaw rather than a defect in deployed Quay instances and is not directly exploitable against Quay itself; no public exploit code was identified at time of analysis, and the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H reflects high attack complexity because successful exploitation depends on first compromising an external dependency and only triggers when the release workflow executes.
Unauthenticated arbitrary Python module import in djust before 1.0.7 lets any client that can reach the WebSocket or SSE mount endpoint force the server to import a module chosen by a client-supplied dotted path, executing that module's import-time side effects before any LiveView subclass check or per-view authentication occurs. The LIVEVIEW_ALLOWED_MODULES allowlist that should constrain this lookup is fail-open (the check is skipped when the setting is unset, which is the framework default) and uses loose startswith matching, so the flaw is reachable in a default configuration; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Impact is bounded by what is already installed and importable on the host: guaranteed outcomes are denial of service (import bombs, expensive dependency trees) and a module/class enumeration oracle exposed through distinct error strings, escalating to RCE-by-proxy where a suitably side-effectful module exists. No public exploit has been identified at time of analysis - the maintainer retains the reproducer privately - and there is no CISA KEV listing.
Unsafe deserialization in the opt-in kedro_datasets_experimental.pytorch.PyTorchDataset connector (kedro-datasets versions 5.0.0 through <9.5.0) allows code execution during pipeline load, because the dataset calls torch.load on .pt files without enforcing weights_only=True and silently drops user-supplied load_args, so even an explicit weights_only override never reached PyTorch. Exploitation requires a PyTorch runtime earlier than 2.6 (where weights_only defaults to False) plus a victim pipeline that loads a checkpoint obtained from an attacker-influenced shared model registry, downloaded checkpoint, or partitioned external dataset; unauthenticated remote attackers can plant the payload but must wait for that user interaction, and pipelines loading only trusted files are unaffected. There is no public exploit identified at time of analysis and no confirmed active exploitation; the vendor-released patch is version 9.5.0, which enforces weights_only=True by default and correctly forwards load_args and save_args.
Arbitrary file write via path traversal in ComfyUI before 0.30.0 lets an attacker place attacker-controlled content anywhere on the host filesystem by supplying a crafted folder_name to the dataset save nodes. According to the vendor vector, no authentication is required (PR:N), but exploitation requires user interaction in the form of the victim loading and running a malicious workflow (UI:P); code execution does not occur immediately and instead follows when the written startup file or package initializer is subsequently loaded. Publicly available exploit code exists (a published PoC walkthrough and a VulnCheck advisory), the affected versions are in default configurations, and the vendor has released a fix in 0.30.0; there is no indication of confirmed active exploitation (CISA KEV), and this is not an unauthenticated remote worm-class flaw despite its 8.5 severity, because the local vector and mandatory workflow-import step constrain delivery.
Refine's @refinedev/inferencer package through version 7.0.0 interpolates API field names straight into generated JSX source without escaping, so an attacker who controls or has compromised the data provider can supply crafted JSON property names that execute as JavaScript in a developer's browser when an Inferencer-generated page renders. Remote, unauthenticated input is possible per the published vector (PR:N), but exploitation is gated on developer interaction (UI:P/UI:R), a malicious or untrusted backend (AC:H/AT:P), and a developer actually previewing Inferencer output - hence our independent assessment rates real-world risk materially below the 7.7 CVSS 4.0 headline, and no public exploit code was identified at time of analysis. The issue is tracked upstream in the refinedev/refine repository as issue #7556.
BC Security Empire before 6.7.1 is affected by an authenticated path traversal vulnerability in its multipart file upload flow; an operator with a valid Empire session can place a traversal sequence in the uploaded filename and write files outside the intended downloads directory on the C2 server, potentially achieving code execution. The issue is fixed in 6.7.1, which validates filenames and resolves upload paths safely; no public exploit identified at time of analysis, and CVSS 4.0 rates it 8.7 (assessed CVSS 3.1 8.8) with high confidentiality, integrity, and availability impact. Exploitation requires network access to the C2 REST API and valid credentials or a hijacked operator session, so patched or access-restricted deployments are not exposed.
HP Advance server software contains a path traversal vulnerability (CWE-22) in its HP AC Print & Scan and HP Output Central components, allowing unauthenticated remote attackers to write arbitrary files, which can lead to remote code execution or privilege escalation. The vendor CVSS 4.0 vector (8.8) rates it network-reachable and unauthenticated with high integrity and availability impact, but HP notes impact occurs 'under certain conditions,' implying unstated deployment prerequisites that may narrow actual exploitability; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated remote code injection in HP Advance can let an attacker with network reachability to the print-management server hosting HP AC Print & Scan or HP Output Central achieve elevation of privilege, remote code execution, or arbitrary file write, as described in HP's self-published advisory hpsbpi04149 (CVSS 4.0 base score 9.3 Critical, CWE-94). The vendor scores both the vulnerable component (VC:H/VI:L) and subsequent systems (SC:H/SI:H) as impacted, and our independent assessment retains a high-severity rating (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) while noting that HP's explicit 'under certain conditions' wording implies a specific feature, endpoint, or deployment mode is a likely precondition despite the AC:L rating. Exploitation requires no authentication and no user interaction per the CVSS vector, but there is no CISA KEV entry, no public exploit code identified at time of analysis, and no affected version range published by the vendor.
Unauthenticated remote code execution and privilege escalation in HP Advance software can lead to full server compromise, but exploitation requires specific, undisclosed configuration or deployment conditions according to HP's advisory. The flaw affects the HP AC Print & Scan and HP Output Central components hosted on the HP Advance server. No public exploit code has been identified at time of analysis, though the vendor's CVSS 4.0 vector rates it 9.3 critical while an independent assessment adjusts attack complexity to High due to the gating conditions.
Arbitrary code execution in Redocly CLI and @redocly/respect-core before version 2.33.0 allows a crafted Arazzo description to run attacker-controlled JavaScript with the privileges of the CLI process. The flaw lives in the `respect` command's `$faker` runtime-expression evaluator (get-value-from-context.ts), which permits property traversal through `constructor`, `prototype`, and `__proto__` to reach the JavaScript Function constructor; because the vector is local (AV:L) with required user interaction (UI:R, PR:N), a victim or CI job must actually process an untrusted, attacker-supplied workflow description for exploitation to occur. Impact is high in CI environments, where the injected code can execute shell commands or read pipeline secrets, while users who only run trusted, self-authored workflows are unaffected; no public exploit code was identified at the time of analysis, but a patch exists in 2.33.0.
Heap-based buffer overflow (CWE-122) in HP's HPLIP - the HP Linux Imaging and Printing Software stack shipped as the default printer/scanner driver on most Linux distributions - can be triggered when attacker-influenced data is processed by a vulnerable component, potentially leading to remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. This is a bundled advisory covering multiple externally reported flaws across several HPLIP components, so the precise prerequisites vary per sub-vulnerability; the vendor assigns CVSS 4.0 score 9.3 (Critical) with a remote, unauthenticated, low-complexity vector, while the independent assessment is more conservative at CVSS 3.1 AV:N/AC:H/PR:N/UI:N, reflecting that the system must be running HPLIP and actually process malicious input. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Arbitrary code execution in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled allows an unauthenticated gNPSI client to craft a malicious request that executes code on the switch, yielding full administrative control of the device. The exploit path is gated by a hard precondition: gNPSI is not enabled by default and the gRPC endpoint must be network-reachable, which the vendor vector captures as AT:P and the advisory describes as 'under certain circumstances'; given that condition, no authentication (PR:N) or user interaction (UI:N) is needed. The vulnerability is rated critical (CVSS 4.0 base 9.2, independent 3.1 assessment AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact), and no public exploit code has been identified at time of analysis, so realistic risk is concentrated on switches where gNPSI has been turned on and exposed to untrusted network segments.
HPLIP (HP Linux Imaging and Printing Software) is affected by multiple heap-based buffer overflow vulnerabilities (CWE-122) that can lead to remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. Exploitation requires user interaction, such as a victim performing a print or scan operation or processing attacker-supplied imaging data, but no authentication is needed, and the attack is network-reachable. HP has remediated the issues; no public exploit code has been identified at the time of analysis.
Heap-based buffer overflow and related memory-safety flaws in HP Linux Imaging and Printing (HPLIP) can allow remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification on Linux hosts where HPLIP is installed and the affected component is active. This is an aggregate HP bulletin (hpsbpi04151) that bundles multiple externally reported issues under one CVE, so the published CVSS 4.0 score of 9.3 (AV:N/AC:L/PR:N/UI:N/VC:H/VI:H/VA:H) represents the worst-case component rather than any single flaw, and the assessed CVSS 3.1 score is lower (AV:N/AC:H) because several sub-issues are more likely local than remote and heap exploitation requires reliable memory grooming. No public exploit code or confirmed active exploitation was identified at time of analysis, and the exposure is limited to Linux systems on which HPLIP is deployed rather than being a universal service.
Command injection weaknesses in HP Linux Imaging and Printing Software (HPLIP) allow a local attacker to execute arbitrary operating-system commands with the privileges of the affected HPLIP component, resulting in high confidentiality, integrity, and availability impact (vendor CVSS 4.0 base 8.4) and spanning remote code execution, privilege escalation, denial of service, information disclosure, and unauthorized file modification. Exploitation is not remote: it requires local access to a Linux host that has HPLIP installed and in use, and it requires active user interaction, typically by inducing a legitimate user to feed attacker-controlled input into a vulnerable HPLIP component that builds an OS command (CWE-78). No authentication or elevated privileges are needed (PR:N), and no public exploit code or confirmed active exploitation was identified at time of analysis; HP has released remediation for the affected components in advisory HPSBPI04151.
Heap-based buffer overflows and related memory-safety flaws in HPLIP (HP Linux Imaging and Printing Software) let remote attackers corrupt memory in the print, scan, and device-discovery stack, potentially yielding remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification. Only Linux hosts with HPLIP installed and actively processing attacker-influenced input - a crafted print job, a rogue printer/scanner response, or a file handled by the HPLIP stack - are affected, and exploitation is gated on active user interaction (initiating or accepting the malicious print/scan operation) rather than being a fully autonomous remote exploit. The flaws are unauthenticated per the vendor CVSS vector (PR:N), impact varies depending on which bundled sub-vulnerability is triggered, and no public exploit identified at time of analysis.
Out-of-bounds write flaws in HPLIP (HP Linux Imaging and Printing Software) can corrupt memory when a user processes attacker-influenced input such as a crafted print job, a malicious device or network response, or a handled file, with the affected product confirmed by HP and documented in advisory HPSBPI04151. No authentication is required to reach the vulnerable components, but exploitation depends on mandatory user interaction and on hosts that actually have HPLIP installed and in active printing or scanning use. Worst-case impact spans remote code execution, privilege escalation, denial of service, information disclosure, and unauthorized file modification; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated remote code execution in Cisco ISE allows an attacker with low-privileged administrative credentials to execute arbitrary commands on the underlying operating system and elevate to root via insecure deserialization of a crafted Java object sent to the web-based management interface. Exploitation requires network access to the management interface and valid low-privileged admin credentials (CVSS 9.9, PR:L), and successful attacks on single-node deployments can cause a denial-of-service condition that prevents unauthenticated endpoints from accessing the network. No public exploit has been identified at time of analysis.
Command injection in the REST API of Cisco ISE and ISE-PIC allows authenticated administrators to execute arbitrary commands with root privileges on the underlying operating system, potentially leading to complete node compromise and, in single-node deployments, a denial-of-service condition. This vulnerability (CVE-2026-20306) requires valid administrative credentials (PR:H) and network access to the management interface; no public exploit code has been identified at the time of analysis. The CVSS 3.1 base score is 9.1, driven by the high impact of root-level code execution and scope change from the web application to the OS.
Cisco ISE and ISE-PIC contain an OS command injection flaw (CWE-78) in their web-based diagnostic tools that lets an authenticated remote attacker with valid administrative credentials execute arbitrary commands and gain root on the underlying operating system. Because the attacker must already hold admin rights (PR:H), this is primarily a privilege-escalation and integrity-risk issue rather than an anonymous entry point, though the CVSS 3.1 score is 9.1 Critical (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) due to the scope change and full loss of confidentiality, integrity, and availability. On single-node deployments, successful exploitation can render the ISE node unavailable and block endpoints that have not yet authenticated from reaching the network, producing a denial-of-service condition; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Path traversal and arbitrary file write in the oras-go OCI artifact library prior to 2.6.2 allow a malicious artifact layer marked with the io.deis.oras.content.unpack=true annotation to escape the content/file.Store extraction root and create or overwrite any file writable by the pulling process, potentially leading to code execution. Exploitation is unauthenticated from an attacker's network position (CVSS:3.1/AV:N/AC:L/PR:N) but requires user interaction (UI:R) because the victim must pull the attacker-controlled artifact reference; the bug bypasses the AllowPathTraversalOnWrite=false default, so no permissive configuration is needed. Scored 8.8 High, with no public exploit identified at time of analysis and no CISA KEV listing; a vendor patch is available in oras-go 2.6.2.
Stack-based buffer overflow in the Dell Update Package (DUP) Framework, affecting versions prior to 26.07.03, allows an unauthenticated attacker on the same local network segment (AV:A) to corrupt stack memory and achieve arbitrary code execution on the affected host with full confidentiality, integrity, and availability impact. Exploitation requires no credentials or user interaction and is low-complexity once the attacker has L2 adjacency to a system running the vulnerable framework, though it is not reachable from the internet and CISA SSVC rates it non-automatable with only partial technical impact. No public exploit code has been identified at time of analysis and EPSS is low (0.30%, 22nd percentile); Dell has released a fixed version.
Zip-slip path traversal in the Stanford NLP Stanza Python library before 1.14.0 lets a malicious model or resource archive write files outside the intended model directory, overwriting anything writable by the Stanza process and potentially achieving code execution via modified shell configuration, SSH authorized_keys, Python packages, or executable scripts. The vulnerable code path is reached when a victim runs stanza.download() or stanza.install_corenlp(); exploitation therefore requires the fetched archive to be attacker-controlled (compromised or malicious mirror, MITM of the transfer, or a victim-supplied resource URL) plus user interaction to initiate the download. Rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and tracked as CWE-22; unauthenticated per the PR:N vector but local and interaction-dependent, with no public exploit identified at time of analysis and a vendor patch available in 1.14.0.
Remote code execution in InternLM LMDeploy versions 0.9.1 through 0.10.1 allows unauthenticated network attackers to run arbitrary commands by sending crafted pickle payloads to the AsyncRPCServer RPC endpoint (zmq_rpc.py). The service deserializes raw messages with pickle.loads() and performs no authentication or IP validation, so any attacker who can reach the randomized port-typically found by scanning-can trigger code execution; publicly available exploit code exists (proof-of-concept with reverse shell demo), and the CVSS 3.1 score is 9.8. This is not confirmed actively exploited (no CISA KEV listing), and exploitation is not possible if the RPC service is bound exclusively to localhost; upgrading to 0.10.2 patches the deserialization flaw and restricts the RPC to localhost.
Authenticated remote code execution in ScadaLTS 2.8.1-release-candidate build 0 allows any holder of a low-privilege account to run arbitrary JavaScript on the server by abusing the scripting sandbox. The DWR-exposed DataSourceEditDwr.validateScript method performs no authorization check and is reachable through a DWR routing bypass, so supplied code is compiled and executed by the Rhino engine with the application's privileges (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status; the independent assessment treats this as a genuine, credible priority rather than an inflated high-CVSS artifact, with the requirement for valid credentials being the principal limiting factor.
Authenticated users who can register or modify a TechDocs documentation source can achieve code execution inside the Backstage TechDocs backend or its build container by supplying a crafted mkdocs.yml, because @backstage/plugin-techdocs-node fails to strip unsafe Python YAML tags, markdown_extensions names and their configuration, theme options, and extra_templates values before the file reaches the Python documentation generator. The flaw affects the techdocs-node plugin before 1.14.6 and the 1.15.0 through 1.15.3 range, and the vendor has released fixes in 1.14.6 and 1.15.4. Authentication is mandatory per the CVSS vector (PR:L), no public exploit code or confirmed active exploitation was identified at time of analysis, and the blast radius is limited to the files, credentials, and network reach of the TechDocs backend or build container rather than the wider Backstage host.
Sandbox escape in RestrictedPython versions prior to 8.4 lets code executing inside the restricted context reach host-level primitives - function globals, builtins, file access, and code-execution gadgets - whenever the host exposes the standard-library string module, the string.Formatter class, a Formatter instance, or a Formatter subclass to that restricted code. The prerequisite is non-default: stock RestrictedPython does not surface these objects, so a custom import policy or specially crafted globals must be in place, and the attacker must also be able to submit restricted Python code (typically an authenticated user of the hosting application). A vendor patch is available in 8.4; no public exploit was identified at time of analysis.
Path traversal in the Jenkins Robot Framework Plugin (6.2.2 and earlier) allows an authenticated user holding Item/Configure permission to point the plugin's report archive directory at a location outside the build directory, giving attacker-chosen file creation or overwrite anywhere on the Jenkins controller filesystem - an impact that can be escalated to remote code execution. The flaw is remotely reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) and requires no user interaction, but it is gated by the Item/Configure privilege, plugin installation and use, and a build actually executing to trigger the write. No public exploit code has been identified at time of analysis, and the risk concentrates on multi-user or multi-tenant controllers where lower-trust users are permitted to configure jobs.
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets an authenticated attacker who holds permission to define classpath entries run attacker-supplied code inside the Jenkins controller JVM. The plugin downloads the URL-specified JAR twice - it verifies approval against the first response but then loads classpath entries from the second - so an attacker who controls the hosting server can present a benign, approvable JAR on request one and a malicious JAR on request two. The assessed CVSS 3.1 vector (7.5, AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects this time-of-check/time-of-use race: the flaw is remotely reachable but requires an authenticated classpath-defining user and a reliably won race; there is no public exploit code and no confirmed active exploitation identified at time of analysis.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-configure privileges defines classpath entries in an item configuration, those entries are silently auto-approved the moment a user holding Overall/Administer permission copies that item or updates its configuration through the REST API or CLI. The result is code execution inside the Jenkins controller JVM (CWE-94, CVSS 8.0), but exploitation is a two-actor, confused-deputy scenario: the attacker needs pre-existing config-edit rights (PR:L) and must wait for a privileged user to perform the copy or API/CLI update (UI:R), so installations where only administrators author jobs and never copy them or drive configuration through REST/CLI are effectively unexposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows an authenticated Jenkins user who holds permission to define and run sandboxed scripts - including Pipelines - to execute code outside the Groovy sandbox by supplying an @Builder annotation whose builderStrategy member names an arbitrary class. Exploitation additionally requires that a suitable "gadget" class be present on the classpath of the component that evaluates the script, which is why the assessment rates it AC:H despite high C:H/I:H/A:H impact and a scope change (S:C) across the sandbox boundary; the limitation is that only instances where untrusted or low-privilege users can author sandboxed scripts are meaningfully exposed. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; EPSS is 0.20% (11th percentile), consistent with a high-severity but precondition-heavy flaw rather than a mass-exploitable internet threat.
Sandbox escape leading to arbitrary code execution inside the Jenkins controller JVM affects Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier because the plugin fails to reject the @GroovyASTTransformationClass annotation in script source. An authenticated Jenkins user with permission to define and run sandboxed scripts, including Pipelines (the CVSS vector carries PR:L), can submit a script that registers a Groovy AST transformation executed at compile time, before the sandbox applies, resulting in high confidentiality, integrity, and availability impact on the controller; our independent assessment scores this 8.8 with a scope change (S:C) rather than the provider's S:U. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but for any account holding script-submission rights the exploit path is direct rather than theoretical, so the practical risk concentrates on instances that grant Job/Configure or equivalent Pipeline-authoring rights broadly. This is a genuine high-priority vulnerability, not CVSS inflation: the sandbox itself, not a misconfiguration, is the control being bypassed.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated attacker with permission to define and run sandboxed Groovy scripts or Pipelines to bypass the sandbox and run code in the Jenkins controller JVM. The flaw is a protection mechanism failure (CWE-693) in how the plugin casts collections, and it carries CVSS 8.8 with PR:L; only users who can author sandboxed scripts or Pipelines can trigger it. No public exploit code was identified at time of analysis, and CISA SSVC rates exploitation as none, but this is high-priority for multi-tenant Jenkins because script-authoring rights are often broadly granted.
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows authenticated users with permission to define and run sandboxed Groovy or Pipeline scripts to execute arbitrary code in the Jenkins controller JVM, because the sandbox fails to intercept method calls, property and attribute accesses, and array accesses made on a null receiver. No non-default configuration is required - the weakness is inherent to the default sandbox - and the flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-693), with CISA SSVC assessing total technical impact but no active exploitation and no public exploit identified at time of analysis. Real-world urgency is moderated by the access prerequisite: the attacker must already hold script-authoring rights, so exposure is concentrated in multi-tenant or delegated Jenkins instances where Pipeline authoring is granted to less-trusted users.
Sandbox escape in the Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier lets an authenticated user who holds permission to define and run sandboxed scripts - including Pipelines - execute arbitrary code in the Jenkins controller JVM, earning a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a protection-mechanism failure (CWE-693): the sandbox proxy created when a script coerces a value to a Java interface skips the method check when the coerced value inherits a same-named method, so the interface proxy can be used to reach unchecked code. No public exploit code has been identified at time of analysis and CISA SSVC rates the issue non-automatable (Exploitation: none, Automatable: no, Technical Impact: total), so mass exploitation is not expected; the binding prerequisite is the authenticated script-authoring permission reflected by PR:L, which makes this a real but privilege-gated RCE-class risk.
Unauthenticated remote code execution affects Check Point Quantum Security Management, where a stack-based buffer overflow is reachable through the login process before authentication completes. Because the flaw is triggered during the pre-authentication login path, a remote attacker with network reachability to the management server's login/administration service needs no credentials, no user interaction, and no non-default configuration, and the resulting code execution is described as running with root privileges - consistent with the CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV), but the pre-auth, root-level impact and the criticality of the management plane make this a top-priority patch target; CPE data lists the product with a wildcard version, indicating the affected version range is not bounded in the available feed data.
Arbitrary Lua code execution is possible on Advantech EKI-1242EIMS and EKI-1242IEIMS industrial Modbus gateways running firmware V1.06.01, because the Modbus CSV import workflow fails to neutralize code embedded in an uploaded configuration file (CWE-94). Exploitation requires an attacker to already hold a high-privilege authenticated session on the device web management interface and to be able to reach that interface over the network, which materially limits exposure in properly segmented OT environments; no user interaction on the part of a legitimate operator is needed, only the attacker's own crafted upload. Successful exploitation yields full loss of confidentiality, integrity, and availability of the device, but no public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (not listed in CISA KEV); the vulnerability was identified by Nozomi Networks Labs and a vendor security advisory has been published.
Code injection in the web management interface of Advantech EKI-1242IEIMS (and the closely related EKI-1242EIMS) industrial gateways on firmware V1.06.01 lets a remote attacker who already holds high-privilege web UI credentials execute arbitrary code on the device, including OS commands running as root. Exploitation is low-complexity once the attacker is authenticated, but the admin credential requirement (CVSS PR:H) is a hard gate that limits exposure to devices whose management interfaces are reachable and whose admin accounts have been compromised, reused, or left at weak/default values. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing); Advantech has published a security advisory for the issue, with Nozomi Networks Labs credited for the discovery. Risk framing: this is a genuine but access-gated risk concentrated on internet- or flat-network-exposed management interfaces rather than on segmented OT deployments.
Unauthenticated remote code execution affects Arista EOS platforms on which the non-default P4Runtime service has been explicitly enabled, letting an attacker who can reach that service take complete administrative control of the switch. The defect is a code-injection flaw (CWE-94) triggered by a crafted packet during P4Runtime session initiation, rated 9.5 Critical under CVSS 4.0 and assessed as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with high attack complexity and a changed scope because compromise of the switching platform can extend to subsequent systems. Exposure is limited: P4Runtime is disabled by default, so stock EOS deployments are not at risk, and successful exploitation also depends on a specific timing/condition requirement (AT:P, 'Attack Requirements: Present'); Arista discovered the issue internally, reports no malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis.
Authenticated remote code execution in Arista EOS allows a malicious client with valid gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch by sending a single specially crafted request. Only switches where gNMI has been explicitly enabled are exposed - gNMI is a non-default management API - and the attacker must already hold working gNMI credentials, which limits practical exposure to insiders or adversaries who have already compromised network-automation or management accounts, but grants them full root control of the device with low attack complexity and no user interaction. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); no EPSS score was provided. The vendor has published security advisory SA-0166 at https://www.arista.com/en/support/advisories-notices/security-advisory/24722-security-advisory-0166.
Heap-based memory corruption in NLnet Labs Unbound up to and including 1.26.0 lets a remote, unauthenticated attacker who controls or spoofs the upstream DNS response (PR:N/UI:N) gradually overwrite heap memory, with the reliable outcome being a crash and remote code execution possible only on certain systems and compilation options that lack hardening. The flaw is scored CVSS 8.4 (CVSS:4.0) and by the independent assessment as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with the high attack complexity reflecting heavy dependence on heap layout and non-deterministic results. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no KEV listing or EPSS signal is present, so this is a genuine but not-yet-urgent priority for internet-facing recursive resolvers.
A crafted DNSKEY whose owner name is a compression pointer into its own RDATA overflows the digest buffer in the DNSSEC validator of NLnet Labs Unbound 1.26.0 and earlier, letting an attacker who controls an authoritative zone crash a validating recursive resolver and, depending on heap layout, potentially execute code with attacker-influenced data. Exploitation is unauthenticated over the network per the CVSS vectors but is gated on DNSSEC validation being active and on inducing the resolver to query a name in the attacker's zone; the independently assessed impact is primarily denial of service (availability High, confidentiality and integrity Low), with remote code execution only possible rather than demonstrated. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, although the vendor rates the issue 9.1 under CVSS 4.0 and an advisory has been published.
Remote code execution is achievable on Pepperl+Fuchs ICE2/ICE3-series IO-Link Master devices and the Phoenix Contact IOL MA8 via a local file inclusion flaw in the `/index.php/ajax/save_iodd_parameters` AJAX endpoint. An authenticated attacker holding a valid operator-level session cookie can supply a crafted filename parameter that causes the PHP runtime to include and execute an attacker-controlled file, yielding full device compromise. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation requires prior acquisition of operator credentials.
Remote code execution via PHP local file inclusion on Pepperl+Fuchs ICE2/ICE3 series IO-Link Master devices and OEM equivalents (Phoenix Contact, Indu-Sol variants) allows a low-privileged authenticated attacker to execute arbitrary PHP code by supplying a crafted parameter to the /index.php/ajax/get_iodd_port_info endpoint. The vulnerability requires only a valid user session cookie, making it accessible to any account holder on these industrial automation gateways. Three separate CERT VDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the same vulnerable firmware is shipped under at least three different vendor brands, broadening the affected fleet across OT environments. No public exploit code or active exploitation has been identified at time of analysis.
Path traversal in Octopus Server allows an authenticated low-privilege user to overwrite arbitrary files on the server filesystem, which in certain configurations escalates to remote code execution. Affected are three distinct release trains of Octopus Server (CPE: cpe:2.3:a:octopus_deploy:octopus_server). No public exploit or CISA KEV listing exists at time of analysis, and a vendor patch is available across all three affected version ranges.
Arbitrary file upload with remote code execution impact in the WordPress plugin WP Import Export Lite affects every version before 3.9.33, allowing an authenticated user who holds the plugin's import permission to make the server fetch a remote file of the attacker's choosing and store it without any validation of type, extension, or content. The plugin's URL-based import path performs no content checks, so executable files can be planted on the host and executed; the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) confirms the low-privileged-but-authenticated prerequisite and no victim interaction. Publicly available exploit code exists, though EPSS is currently low at 0.25% (17th percentile), reflecting the limited population of sites that both run the plugin and expose the import capability; a vendor fix is available in 3.9.33. This is a genuine priority for any site running WP Import Export Lite before 3.9.33, tempered by an authentication prerequisite.
Unrestricted PHP function invocation in the WP Import Export Lite WordPress plugin before 3.9.33 allows a user holding the plugin's export permission to achieve remote code execution by applying arbitrary PHP functions to exported field values they control. Exploitation requires an authenticated, high-privilege account (PR:H in the assessed CVSS vector) that can configure and run an export, needs no user interaction, and is network-reachable. Publicly available exploit code exists, though EPSS is low at 0.27% (20th percentile) and there is no CISA KEV listing; the vendor has released a fix in version 3.9.33.
Remote code execution in the WP Import Export Lite WordPress plugin before 3.9.34 requires an authenticated user who has been granted the plugin's export permission, a privileged, non-default capability typically held by administrators or trusted operators. The plugin does not validate the user-supplied output path or filename when its export routine writes files, so that user can write a file with an arbitrary name - for example a .php webshell - into an arbitrary web-accessible directory and have it executed with the web server's privileges. Publicly available exploit code exists, but the flaw is not listed in CISA KEV, there is no confirmed active exploitation, and EPSS is low at 0.27% (20th percentile); the vendor has released 3.9.34 as the fix.
Arbitrary file overwrite in the Contest Gallery WordPress plugin (Upload & Vote Photos, Media, Sell with PayPal & Stripe) affects all versions up to and including 32.0.1, where the 'baseUrlForFacebook' parameter is passed to a file-writing routine without adequate path validation. Exploitation requires at least a subscriber-level account on the target WordPress site, but then allows overwriting known files on the server, which can escalate to remote code execution when the overwritten path is a PHP file that the web server later executes. No public exploit code or CISA KEV listing was provided in the source data for this CVE, so active exploitation is unconfirmed at time of analysis.
Local privilege-abuse code execution affects Howyar Technologies' SysReturn disk-protection solution in all versions prior to 11.3.034 (fixed in v11.3.0.34): a privileged local attacker who can write to the EFI System Partition can drop the SysReturn UEFI loader (BOOTia32.efi) alongside a crafted cloak32.dat data file, which the trusted boot-time component parses and executes code from at the next boot. Exploitation requires ESP write access - admin/root on a running system, or physical/offline access to the machine or its boot media - so this is a local vector (AV:L) with PR:H per the assessed vector, not a remote or unauthenticated path; CISA KEV does not list active exploitation, though public exploit code is referenced via the linked GitHub researcher repositories. Practical risk is concentrated on SysReturn-protected endpoints such as kiosks, shared lab PCs, and locked-down workstations where an insider or a prior compromise can modify the ESP and then achieve boot-time code execution with high confidentiality, integrity, and availability impact.
Arbitrary code execution in Sogou Input Method versions before 16.3.0.3498 allows a remote attacker to run code through the biz_helper.exe helper component on Windows. The vendor CVSS vector is AV:N/AC:L/PR:N/UI:N (9.8), but the independent assessment rates the vector as AV:N/AC:L/PR:N/UI:R, meaning a victim likely must interact with attacker-controlled content for exploitation. No public exploit identified at time of analysis, and upgrading to 16.3.0.3498 or later is the confirmed fix.
Heap-based buffer overflow in GIMP's file-psd import plugin allows a crafted PSD file to corrupt adjacent heap memory, causing an application crash or potentially arbitrary code execution when the user opens the file or when a thumbnail preview is generated for it. The root cause is an integer overflow (CWE-190) in the multiplication of values taken from an embedded JPEG header, which yields an undersized heap allocation that is subsequently overrun during image decoding and can be turned into a controlled memory write. The assessed vector (CVSS 3.1, 7.8 High, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms this is a local, user-interaction-dependent flaw rather than a remotely reachable service bug, so exploitation requires delivering the malicious PSD to a machine where GIMP or an automatic PSD thumbnailer processes it; no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV.
Remote compromise of Oracle GraalVM is possible: an unauthenticated attacker with HTTP access can exploit a defect in the Compiler component to achieve full takeover of the affected runtime, with high confidentiality, integrity and availability impact. Affected builds are Oracle GraalVM for JDK 17 (23.0.13.1), Oracle GraalVM for JDK 21 (23.1.12.1) and Oracle GraalVM 25 (25.0.4.1). No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, so exploitation is currently assessed as targeted rather than opportunistic; note that the accompanying 'Information Disclosure' tag understates the stated impact.
A stack-based buffer overflow in the Netcore NR255-V router (firmware 1.5.130703) allows an attacker who can reach the web management interface to smash a fixed-size stack buffer by submitting oversized form values to the ntools_tcpdump_start_set.cgi endpoint, which passes input to an unsized sprintf call. Successful exploitation can corrupt the saved return address and potentially lead to arbitrary code execution with the privileges of the CGI process on the device. The supplied CVSS 4.0 vector (8.7) rates confidentiality, integrity and availability impact as high with a network vector, but PR:L indicates some level of authentication or low-privilege access is required; no EPSS score, CISA KEV listing, or confirmed public exploit code was included in the intelligence feed, and no vendor patch reference was provided.
PHP object injection in the Cotonti 1.0.0 Comments plugin allows unauthenticated, network-reachable attackers to instantiate arbitrary PHP classes with attacker-controlled properties by feeding a crafted base64-encoded payload through the `ci` GET parameter, which is passed to unserialize() without an allowed_classes restriction. Any default Cotonti 1.0.0 deployment with the Comments plugin enabled and its widget rendering is exposed; no credentials or user interaction are required, and successful gadget-chain abuse can lead to database manipulation or remote code execution. No public exploit code was identified at time of analysis, and there is no confirmed active exploitation (CISA KEV), though the vendor has published an upstream fix via pull request #1889 that hardens the deserialization call.
Use-after-free in the Workers component of Google Chrome allows an unauthenticated remote attacker to execute arbitrary code outside the browser sandbox when a victim renders a crafted HTML page in any build prior to 153.0.8010.47, including default desktop installations on Windows, macOS and Linux. The only prerequisite is user interaction - opening or being lured to the malicious page (UI:R) - with no special configuration or prior access needed, and because the flaw yields a scope change the compromise extends to the host rather than remaining confined to the renderer. Google rates the issue Critical and has shipped a fixed build; exploitation is not currently observed, CISA's SSVC assessment classifies the flaw as not automatable, and no public exploit identified at time of analysis, though the combination of network reachability, low attack complexity and total technical impact makes it a genuine high-priority vulnerability for prompt patching.
A time-of-check-to-time-of-use race condition in the Extensions component of Google Chrome on macOS allows an attacker to break out of the renderer sandbox and execute arbitrary code in the browser process context. The barrier to entry is meaningful: the attacker must already have compromised the renderer process through a separate bug and then use social engineering to persuade the victim into a specific UI interaction that widens the race window. Affected builds are Chrome for macOS prior to 153.0.8010.47, and Google rates the issue High severity; no public exploit code or CISA KEV entry was identified at time of analysis.
Use-after-free in the V8 JavaScript engine of Google Chrome desktop builds prior to 153.0.8010.47 allows unauthenticated remote attackers to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. Because the CVSS vector is PR:N/UI:R, no credentials or special browser configuration are required, but the victim must actively navigate to attacker-controlled content; the memory-corruption primitive is confined to the renderer process, so full host compromise would require a second, independent sandbox-escape vulnerability. No public exploit code has been identified at time of analysis, and the vendor has released a fixed build, making this a high-priority patch item rather than a confirmed active-exploitation emergency.
Sandbox escape in Google Chrome prior to 153.0.8010.47 allows a remote attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox via a race condition (TOCTOU) triggered by a crafted HTML page; the user must visit that page for the flaw to be reachable. Google rates the issue Chromium security severity High and a vendor patch is available from the 153.0.8010.47 stable channel release. There is no public exploit code and no CISA KEV listing at time of analysis, and the high attack complexity combined with a required renderer-compromise precondition keeps realistic risk below the raw 8.3 CVSS score.
Type confusion in Chrome's CacheStorage implementation in builds prior to 153.0.8010.47 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page. The bug is rated High by Chromium and 8.8 by NVD (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), but it is a renderer-level compromise rather than a sandbox escape, so host impact requires chaining a second vulnerability. No CISA KEV listing and no public exploit code were identified at time of analysis, and no EPSS score was supplied in the input data.
Improper input validation in ANGLE, Google Chrome's graphics abstraction layer, allows a remote attacker to potentially execute arbitrary code outside the browser sandbox by convincing a user to open a crafted HTML page in Chrome builds prior to 153.0.8010.47. Exploitation requires no authentication (PR:N) but does require user interaction (UI:R) - the victim must navigate to attacker-controlled or compromised content - and the scope-change metric (S:C) reflects that successful exploitation implies code execution escaping the renderer sandbox onto the host OS. The issue carries a Critical 9.6 CVSS rating and a vendor patch is available in Chrome 153.0.8010.47; there is no public exploit identified at time of analysis, and Chromium rates the underlying security severity as Medium.
Remote code execution inside the renderer sandbox can be triggered in unpatched Google Chrome builds by a use-after-free in the browser's built-in PDF rendering component. Exploitation is unauthenticated (CVSS PR:N) but requires the victim to open a crafted HTML page that embeds malicious PDF content (UI:R), and any resulting code execution is confined to Chrome's renderer sandbox - meaning this bug alone does not compromise the host and would typically need to be chained with a separate sandbox-escape flaw for full system compromise. A vendor patch is available in Chrome 153.0.8010.47; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the 8.8 CVSS score and the ubiquity of Chrome make timely patching a priority.
Use-after-free in Chrome's DOM implementation allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.47. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High by Chromium security severity; a vendor patch is available and no public exploit code or CISA KEV entry was identified at time of analysis.
Google Chrome versions earlier than 153.0.8010.47 contain an incorrect authorization flaw (CWE-863) in the WebUI subsystem that lets an attacker who already controls a compromised renderer process break out of the browser sandbox and run arbitrary code on the host via a crafted HTML page. Exploitation is a two-stage proposition: the attacker must first obtain renderer code execution, then chain this flaw to escape the sandbox, and the victim must load the malicious page. Google rates the Chromium security severity as High and has shipped a fix in Chrome 153.0.8010.47; no public exploit code or CISA KEV entry was identified in the available intelligence at time of analysis.
Incorrect authorization in Chrome's Core component on Windows (versions prior to 153.0.8010.47) lets a local attacker who can run a program on the machine break out of the browser sandbox and execute arbitrary code at the user's privilege level outside it. The flaw is rated High by the Chromium security team and carries CVSS 7.4 (AV:L/AC:H/PR:N/UI:N, C/I/A all High), reflecting a local-only but complete confidentiality, integrity and availability impact once the sandbox boundary is crossed. No public exploit code or CISA KEV listing was provided in the input, and Google has released a fixed stable-channel build, so this is best treated as a high-value chaining primitive rather than a currently mass-exploited issue.
Remote code execution inside the renderer sandbox affects Google Chrome desktop builds prior to 153.0.8010.47, caused by a type confusion flaw in the browser's compositing pipeline (CWE-843) that is reachable from a crafted HTML page. An attacker needs only to convince a user to load the page: the CVSS 3.1 vector is 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so no credentials or privileges are required, but user interaction is mandatory. Google rates the issue Chromium security severity High and has shipped a fixed stable-channel build; no public exploit code or CISA KEV listing appears in the supplied intelligence, and no EPSS score was provided, so the current exploitation picture is best described as patch-now-but-not-known-exploited.
Use-after-free in Google Chrome's DigitalCredentials component lets a remote, unauthenticated attacker execute arbitrary code outside the browser sandbox when a victim is socially engineered into loading a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47. Exploitation requires no credentials or elevated privileges (CVSS PR:N) but does require the user to navigate to the attacker-controlled page (UI:R), and the resulting scope change (S:C) means impact extends beyond the browser's sandbox boundary to full confidentiality, integrity, and availability loss. Google rates the issue High and has shipped a fix in the stable channel; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, so the current risk is driven by the ease of phishing/malvertising delivery rather than confirmed active exploitation.
Integer overflow in V8, Chrome's JavaScript engine, allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in Chrome builds prior to 153.0.8010.47; the bug carries a high CVSS (9.6 as published, scored 8.8 under our scope-unchanged reassessment) because memory corruption in V8 can be leveraged for code execution, though impact is confined to the renderer process and full host compromise would require chaining a separate sandbox-escape flaw. Chrome ships on a rapid auto-update cadence and a vendor patch is available (153.0.8010.47), which limits mass exposure; EPSS is a modest 0.36% (30th percentile), CISA SSVC records no observed exploitation, and no public exploit code has been identified at time of analysis, so this is a high-severity memory-safety defect to prioritize for unpatched or update-delayed enterprise fleets rather than an active-emergency. No authentication is required (PR:N), but exploitation depends on user interaction: the victim must load attacker-controlled JavaScript with scripting enabled in the default configuration.
Let me synthesize. CVE-2026-91727: Incorrect reference resolution in Extensions in Chrome on Mac prior to 153.0.8010.47. Local attacker who compromised renderer process could execute arbitrary code outside sandbox via a local program. CWE-706 (Use of Incorrectly-Resolved Name or Reference). CVSS 8.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Product: Google Chrome (macOS). Product name 1-3 words: "Google Chrome". Prevalence: ubiquitous. Now fields. Summary: must not copy description; start with impact verb and product. E.g. "Sandbox escape in Google Chrome on macOS (prior to 153.0.8010.47) lets an attacker who has already compromised the renderer process escalate to code execution outside the browser sandbox..." Technical context: CWE-706 incorrect reference resolution in Extensions — extension API resolves a reference (name/path/identifier) incorrectly, allowing a local program to be loaded/executed outside sandbox. macOS-specific. Renderer compromise prerequisite. Risk assessment: CVSS 8.1 with AV:L AC:H PR:N UI:N S:C. EPSS not provided, KEV not provided. Patch available. No POC known. Attack requires renderer compromise (two-stage). S:C indicates sandbox escape crossing security scope. Not KEV → no public exploit identified at time of analysis. Note missing EPSS/KEV data explicitly. Affected products: Google Chrome on macOS versions prior to 153.0.8010.47; EUVD lists "Chrome 153.0.8010.47 <153.0.8010.47" which is malformed/likely means before 153.0.8010.47. Reference: chromereleases blog, chromium issue 516893912. Remediation: upgrade to 153.0.8010.47 or later. Chrome auto-update. macOS-specific. Compensating controls: restrict extension installs via enterprise policy, disable extensions, etc. Trade-offs. Exploit scenario: attacker chains a renderer RCE (e.g. via malicious web content) then exploits the extension reference resolution flaw to break out of sandbox and run native code on macOS host. Exploitation conditions: requires (1) macOS platform, (2) att
Google Chrome builds prior to 153.0.8010.47 carry a use-after-free in the browser's Input component that allows an attacker who already controls a compromised renderer process to escape the Chrome sandbox and run arbitrary code with the browser's privileges. Exploitation is not remote-standalone: it requires a chained renderer compromise plus a victim who opens a crafted HTML page, which is why the flaw is scored High (8.3) rather than Critical despite total technical impact. Google has shipped a fixed stable-channel build; no public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis.
Use-after-free in Google Chrome's Input handling allows a remote attacker to achieve code execution in affected desktop builds prior to 153.0.8010.47. Exploitation is unauthenticated (PR:N) but requires the victim to render attacker-controlled HTML (UI:R), making drive-by or malicious-page delivery the primary vector; default configurations are affected with no non-default prerequisites. The vulnerability is rated CVSS 8.8 (C:H/I:H/A:H) and a vendor patch is available in the Stable channel build 153.0.8010.47; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
A use-after-free in Google Chrome's Internals component allows a remote attacker to potentially execute arbitrary code outside the browser sandbox when a victim opens a crafted HTML page, affecting all Chrome builds prior to 153.0.8010.47 on desktop. Exploitation requires user interaction (visiting the page) but no authentication or elevated privileges, and Google rates the Chromium security severity as Critical. Vendor-released patch: 153.0.8010.47. There is no public exploit code identified at time of analysis and no confirmed actively exploited (CISA KEV) status, though the SSVC framework assigns total technical impact.
Code injection in XML handling in Google Chrome versions prior to 153.0.8010.47 could let a remote attacker bypass the web origin policy by luring a victim into opening a crafted HTML page (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N per independent assessment, versus Google's published 8.1 vector). Exploitation requires user interaction - the victim must load the malicious page - and no authentication is needed, while Google's own Chromium severity rating is 'Low', indicating constrained real-world impact; the EPSS score is 0.26% (17th percentile) and no public exploit has been identified at time of analysis. A vendor patch is available in Chrome 153.0.8010.47, and Chrome's automatic background update mechanism rapidly retires vulnerable versions.
Use-after-free in Google Chrome's Core component lets a remote attacker execute arbitrary code outside the browser sandbox by getting a victim to load a crafted HTML page in any build prior to 153.0.8010.47. The flaw is unauthenticated (PR:N) but requires user interaction (UI:R), and because the resulting code execution occurs outside the sandbox, Chrome's normal renderer isolation does not contain the compromise; the assessed severity is 9.6 with scope changed (S:C). No public exploit code has been identified at time of analysis, and a vendor-released patch is available in Chrome 153.0.8010.47.
Use-after-free in Google Chrome's Auth component allows a remote attacker to achieve code execution outside the browser sandbox when a victim simply loads a crafted HTML page in any desktop Chrome build prior to 153.0.8010.47. Exploitation is unauthenticated and requires no special configuration - the only prerequisite is the user interaction of visiting or rendering the attacker-controlled page (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6), and because the flaw is not confined to the renderer, no separate sandbox-escape bug is needed to reach the host. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Google has released a fixed build (153.0.8010.47), and details remain restricted in the Chromium tracker until most users have updated.
Type confusion in Chrome's ServiceWorker implementation allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by enticing a victim to load a crafted HTML page in any Chrome build prior to 153.0.8010.47. Exploitation is unauthenticated (PR:N) but requires user interaction (UI:R) - the victim must visit or be redirected to attacker-controlled content - and the resulting code execution is confined to the sandbox (S:U), so full host compromise would require chaining a separate sandbox-escape flaw. There is no public exploit identified at time of analysis, and a vendor-released patch (153.0.8010.47) is available, making this a high-priority but practically bounded patching task rather than an urgent zero-day response.
Google Chrome on macOS versions prior to 153.0.8010.47 contain a race condition (TOCTOU) in the Extensions subsystem that lets an attacker who has already compromised the browser's renderer process break out of the sandbox and execute arbitrary code on the host, triggered when a victim loads a crafted HTML page. Google rated the issue High severity and Chromium's own severity assessment drove the 8.3 CVSS base score with a Scope change (S:C), reflecting that code execution crosses the renderer/sandbox boundary rather than staying contained. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch is available and should be applied promptly because sandbox escapes are the high-value second stage of any Chrome exploit chain.
An out-of-bounds write in Google Chrome's ServiceWorker implementation allows remote code execution inside the browser's renderer sandbox when a victim loads a crafted HTML page; exploitation requires the user to visit or be redirected to attacker-controlled content and to have a service worker exercised (UI:R, PR:N), so no credentials or pre-existing privileges are needed. Successful exploitation yields high confidentiality, integrity and availability impact within the sandboxed renderer process (CVSS 3.1 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and host compromise would additionally require a separate sandbox-escape. Only Chrome builds prior to 153.0.8010.47 are affected, a vendor patch is available, and no public exploit code has been identified at time of analysis; because Chrome auto-updates in the background, most installations will remediate themselves quickly, though managed and long-lived sessions should be verified.
Use-after-free in Google Chrome's WebAppInstalls component allows a remote, unauthenticated attacker to execute arbitrary code outside the browser sandbox when a victim loads a crafted HTML page on any build prior to 153.0.8010.47. Exploitation requires user interaction (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6), and the scope-changed rating reflects that a successful attack escapes the renderer sandbox and reaches the host rather than staying contained in the browser process. At time of analysis there is no indication of active exploitation and no public exploit code identified; the vendor has shipped a fixed build (153.0.8010.47) and the primary exposure is unpatched consumer and enterprise Chrome installations.
Type confusion in Google Chrome's ServiceWorker implementation before version 153.0.8010.47 allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by getting a user to open a crafted HTML page. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R), the classic memory-corruption profile for Chrome renderer bugs, and Google rated it High in its Chromium severity scheme. A vendor patch shipped in the 153.0.8010.47 stable release, and there is no public exploit code identified and no CISA KEV entry at time of analysis, so this is a prioritise-and-patch issue rather than a confirmed active campaign.
Unauthenticated remote code execution in Tencent Mass Service Engine in Cluster (MSEC) lets a network-positioned attacker submit a crafted POST request containing ../ sequences to escape the intended upload directory, drop a webshell, and execute arbitrary commands with root privileges on the host. The exploitability signals are uniform: the vendor-assigned CVSS 4.0 base score of 9.3 with vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H describes a remote, low-complexity attack requiring no authentication and no user interaction, and our independent assessment (CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reaches the same conclusion. The practical limiting factor is deployment footprint rather than attack difficulty: MSEC is a niche open-source distributed backend framework, so real-world risk depends on whether a target actually runs MSEC and exposes its HTTP/upload request-handling service to the attacker's network; exploitation status is no public exploit identified at time of analysis (no CISA KEV entry and no published PoC in the supplied intelligence).
Authenticated attackers holding administrative access to the management plane of HPE Networking EdgeConnect SD-WAN Gateways can supply crafted input to an affected component and achieve arbitrary command execution as root. The flaw affects multiple released trains — 9.4.x up to 9.4.8.2, 9.5.x up to 9.5.8.1, 9.6.x up to 9.6.3.1, and 9.7.0.0 — with a CVSS base score of 7.2 reflecting the high privilege prerequisite against total loss of confidentiality, integrity, and availability. There is no CISA KEV entry, no EPSS score, and no public exploit code identified at time of analysis, so this is currently a high-impact but credential-gated risk rather than an actively exploited one.
Authenticated attackers who already hold administrative privileges on HPE Aruba EdgeConnect SD-WAN Gateways can supply specially crafted configuration data that overflows a stack buffer in the configuration processing logic, potentially yielding remote code execution as root or crashing the gateway into a denial of service. The flaw affects gateway releases in the 9.4.x (≤9.4.8.2), 9.5.x (≤9.5.8.1), 9.6.x (≤9.6.3.1) and 9.7.0.0 branches per the ENISA EUVD affected-version list, and carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). No public exploit code, CISA KEV listing or EPSS score was included in the supplied intelligence, so the observed exploitation status is unconfirmed at time of analysis.
Unauthenticated remote code execution and denial-of-service in HPE Aruba Networking EdgeConnect SD-WAN Gateways (versions 9.4.0.0–9.4.8.2, 9.5.0.0–9.5.8.1, 9.6.0.0–9.6.3.1, and 9.7.0.0) arise from flawed parsing of malformed or truncated packets in the proxy packet-processing path, where incorrect length arithmetic triggers an integer overflow that can become a memory-corruption (buffer overflow) condition. Successful exploitation can let a network-positioned attacker execute code or crash the gateway, taking down the SD-WAN overlay. The HPE advisory at support.hpe.com confirms affected version ranges, but there is no CISA KEV listing, no EPSS score, and no public exploit code identified at time of analysis, so this is currently a patch-now, watch-for-exploitation item rather than a confirmed active campaign.
A limited buffer overflow in the network security monitoring component of HPE EdgeConnect SD-WAN Gateways allows an unauthenticated remote attacker to crash the appliance and potentially execute code by driving crafted traffic into the monitoring parser. ENISA EUVD lists four affected release trains: 9.4.0.0 through 9.4.8.2, 9.5.0.0 through 9.5.8.1, 9.6.0.0 through 9.6.3.1, and 9.7.0.0. No CISA KEV entry and no public exploit code were identified at time of analysis, and no EPSS data was supplied with the record.
A buffer overflow in the underlying operating system of HPE Aruba Networking EdgeConnect SD-WAN Gateways lets an unauthenticated attacker on an adjacent network segment execute arbitrary code as a privileged OS user, resulting in full compromise of the appliance. Affected branches span the 9.4.x, 9.5.x, 9.6.x and 9.7.0.0 release trains (up to 9.4.8.2, 9.5.8.1, 9.6.3.1 and 9.7.0.0 respectively). The vendor describes exploitation as conditional on preconditions outside the attacker's control, and no public exploit code, EPSS score or CISA KEV entry was present in the supplied intelligence at time of analysis.