2026-09-16
Sandbox escape in the Avast/AVG/Norton sandbox minifilter driver (aswSnx.sys) on Windows allows an authenticated, low-privileged process already executing inside the sandbox to break file isolation and escalate to SYSTEM (CVSS 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-281). The driver opens the virtualization target with only GENERIC_WRITE and FILE_WRITE_ATTRIBUTES, omitting WRITE_DAC, so every attempt to reapply the original DACL fails silently and virtualized copies of sensitive files are left with permissive permissions; the IRP_MJ_CREATE handler additionally fails to strip WRITE_DAC for sensitive directories, letting a sandboxed process rewrite the security descriptor of a virtualized object, read the virtualized SAM copy, extract local NTLM hashes and run code as SYSTEM. Publicly available exploit code exists (the PrettyPrague proof of concept), the vendor has released patches for the affected Avast, AVG and Norton products, and no CISA KEV entry indicates confirmed active exploitation.
Authenticated users of zlt2000 microservices-platform through 6.0.0 can overwrite the password of any non-administrator account by calling the PUT /users/password endpoint with an arbitrary user id and a new password, because the server never verifies the current password. The flaw is network-reachable, low-complexity, and requires only a low-privilege login session (CVSS 4.0 base 8.7; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:L), and publicly available exploit code exists. Exploitation is limited to non-administrator accounts and is not possible pre-authentication, but a successful attack yields full credential takeover of the targeted account.
Missing authorization in zlt2000 microservices-platform through 6.0.0 lets any authenticated account - including one with zero assigned roles - invoke administrative APIs for user management, role assignment, password resets by user ID, and Elasticsearch index deletion, because the shipped default of zlt.security.auth.urlPermission.enable is false and suppresses all permission checks once authentication succeeds. Exploitation is not pre-auth: it requires a valid low-privilege session against a deployment running the out-of-the-box configuration, and publicly available exploit code exists (VulnCheck-reported PoC scripts covering role-granting, user enumeration, password reset, and ES index deletion), though no confirmed active exploitation (CISA KEV) has been recorded. Assessed severity is high (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8; vendor-published CVSS 4.0 score 8.7) because a zero-role user obtains both read and write access to sensitive administrative functions.
Insufficient scope validation in GitLab Enterprise Edition lets an authenticated user holding only Developer permissions run security policy test pipelines inside projects in their own group and read protected CI/CD variables that are meant to be restricted to Maintainer or Owner roles. All EE releases from 19.0 up to 19.1.8, 19.2.6 and 19.3.2 are affected, and GitLab shipped fixes in those patch releases. Publicly available exploit code exists (a HackerOne report is referenced), but there is no confirmed active exploitation and no CISA KEV listing.
Improper sanitization of user-controlled data in GitLab CE/EE's Markdown JSON table renderer allows crafted content to make a targeted user's browser issue unintended state-changing HTTP requests when the rendered page is viewed, affecting versions from 15.3 through 19.1.7, 19.2.5 and 19.3.1. Exploit details are publicly available through a linked HackerOne report, and the vendor CVSS of 8.2 reflects network reachability, a high attack-complexity rating, required user interaction and a scope change. Vendor-released fixes are 19.1.8, 19.2.6 and 19.3.2.
Unauthenticated denial of service in GitLab CE/EE caused by flawed resource accounting in the GraphQL complexity calculation logic, allowing a crafted query to consume disproportionate server resources. Exploitation affects GitLab 18.4.6 through 19.1.7, 19.2.0 through 19.2.5, and 19.3.0 through 19.3.1 - any Internet- or network-reachable instance with the GraphQL API enabled. Public exploit code exists (a HackerOne report is cited as the source), but there is no CISA KEV listing confirming active in-the-wild exploitation at time of analysis.
Unauthenticated denial of service in GitLab CE/EE (all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2) allows a remote attacker with no credentials to exhaust server resources through the GraphQL API by submitting queries whose true cost the complexity calculation under-counts. The flaw is an improper resource-allocation limit (CWE-770), scored CVSS 7.5 with the entire impact on availability (A:H) and none on confidentiality or integrity. Publicly available exploit code exists - a HackerOne report is linked from the advisory - but there is no CISA KEV listing, so active in-the-wild exploitation is not confirmed; EPSS data was not supplied with this record.
Arbitrary file deletion in zlt2000 microservices-platform through 6.0.0 allows authenticated attackers to delete any user's files and metadata due to missing ownership validation in the file-center module's DELETE /files/{id} endpoint. Attackers can enumerate file identifiers via GET /files and then delete arbitrary files, bypassing authorization controls (CWE-639); publicly available exploit code exists. Exploitation requires a valid, low-privilege account (PR:L) with access to the file-center REST API, and the impact is limited to integrity and availability (no data disclosure), with a CVSS 4.0 base score of 7.2.
Authenticated attackers can read arbitrary Elasticsearch indices in zlt2000 microservices-platform through 6.0.0 by supplying any index name in the POST /search/{indexName} or GET /agg/requestStat/{indexName}/{routing} endpoints, bypassing authorization checks. This exposes sensitive data such as the sys_user index containing user records and password hashes; the vulnerability has a CVSS 4.0 base score of 7.1 and an assessed CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact with no integrity or availability effect. Publicly available exploit code exists (no CISA KEV confirmation), and exploitation requires only a valid low-privilege session on a network-reachable search-center service.
Authenticated back-office users of yshop-crm through 2.1.3 can enumerate the complete user directory via GET /admin-api/system/user/page because the endpoint's @PreAuthorize('system:user:list') gate is commented out in UserController.java. The flaw is a broken-access-control issue (CWE-862) that requires valid admin-panel credentials plus a role configured with data scope ALL; without that scope the query returns little of value, but with it an attacker can harvest login names, nicknames, departments, emails, mobile numbers, and last-login metadata. Publicly available exploit code exists (a Python enumeration PoC), and no CISA KEV entry confirms active exploitation at time of analysis. The independent assessment rates this CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning authenticated remote confidentiality loss only - no integrity or availability impact.
Missing authorization in yshop-crm 2.1.3 and earlier lets any authenticated back-office (admin-api) user delete arbitrary approval-workflow steps via DELETE /admin-api/crm/flow/delete-step, bypassing the permission check that should restrict this to workflow administrators. The result is an integrity-only compromise of the approval chains that gate contract, receivable, and invoice finalization; there is no confidentiality or availability impact, and the CVE record's CVSS 4.0 score of 7.1 maps to an independent CVSS 3.1 assessment of AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, i.e. a genuine but moderate-priority missing-authorization flaw rather than a critical takeover. Publicly available exploit code exists (a Python PoC against the delete-step endpoint); no CISA KEV listing or other confirmation of active in-the-wild exploitation was present in the supplied data.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user - including low-privilege operators - to read the installation-wide audit trail by calling GET /admin-api/crm/operatelog/page, exposing operator names, display nicknames, client IP addresses, User-Agent strings, request URLs, action details, and customer identifiers. Publicly available exploit code exists (a PoC script that queries the endpoint), and although exploitation requires a valid back-office session with network reach to the admin API, no elevated role or user interaction is needed, so the realistic threat is a malicious insider or anyone who has reused or stolen an operator credential. The vulnerability is broken access control (CWE-862) with high confidentiality impact only; it does not permit data modification, service disruption, or pre-authentication compromise.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user to claim and reassign sales leads belonging to other employees by invoking the CrmCluesController receiveCustomer lead-claim endpoint with a manipulated ownerUserId value. The flaw is a broken access control (CWE-862) issue that requires only a valid low-privilege staff login and no administrative role, feature toggle, or user interaction, with the practical impact limited to integrity of lead ownership data (no confidentiality or availability impact). Publicly available exploit code exists in the form of a Python proof-of-concept targeting the endpoint, and the absence of access logging or quota validation on the operation removes any built-in brake on bulk lead theft, though no confirmed active exploitation (CISA KEV) has been observed at time of analysis.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user to issue arbitrary invoices by calling the PUT /admin-api/crm/invoice/issue endpoint, which performs no permission check on the caller. An attacker holding low-privileged back-office credentials can set an invoice's status, overwrite contract invoiced amounts with attacker-chosen values, and trigger invoice emails to arbitrary recipient addresses - a pure integrity impact with no confidentiality or availability loss. Publicly available exploit code exists (a Python PoC in the LinYuanyi1 cve-request-poc repository), but there is no evidence of confirmed active exploitation (CISA KEV).
Missing authorization in yshop-crm through 2.1.3 lets any authenticated back-office user, regardless of role or privilege level, invoke the saveRedisSet and getRedisSet endpoints in CrmCustomerController and rewrite the installation-wide Redis keys that drive lead allocation and customer auto-recycling. Because the scheduled CustomerAutoJob consumes those same keys, a low-privilege staff account can disable recycling, block customer creation, or trigger mass customer deletion across the deployment; publicly available exploit code exists (the VulnCheck-referenced CVE request PoC on GitHub), while no active exploitation has been confirmed and the CVE is not listed in CISA KEV. This is a genuine but bounded-priority issue: exploitation requires a valid CRM account (assessed CVSS PR:L, so unauthenticated remote abuse is not possible), and the assessed impact is high integrity loss to shared policy state (I:H) with a limited availability effect (A:L) and no confidentiality loss (C:N - the readable values are configuration/policy keys, not customer records).
Command injection in Pepperl+Fuchs ICE2/ICE3 IO-Link Master devices (and OEM equivalents from Phoenix Contact and others) allows a low-privileged authenticated attacker to execute arbitrary OS commands as root via the PHP endpoint /index.php/ajax/get_iodd_menu_info. Any valid user or operator account - the lowest access tiers on the device - is sufficient to achieve full device compromise. No public exploit has been identified at time of analysis, but the vulnerability is straightforward (CWE-78) and reported across three separate CERTVDE advisories covering multiple vendor SKUs, indicating a shared firmware base.
Local privilege escalation in Qualitysoft Corporation's QND endpoint management client for Windows (Advance ≤Ver.11.0.9i, Premium and Standard ≤Ver.11.1i) allows any logged-in user to execute arbitrary commands with SYSTEM privileges by abusing an improperly access-controlled named pipe exposed by the client component. The named pipe lacks a restrictive DACL, permitting user-mode processes running under low-privileged accounts to communicate with the SYSTEM-level pipe server and direct it to execute attacker-controlled commands. No public exploit code and no CISA KEV listing have been identified at time of analysis; JPCERT/CC and Qualitysoft Corporation have both published advisories.
Memory-exhaustion denial of service in the official RabbitMQ Go AMQP 0.9.1 client library (amqp091-go) prior to 1.13.0 lets a malicious or compromised broker kill client processes: when a content header frame arrives, the client preallocates the message body buffer using the broker-declared 64-bit body size without capping that hint to the negotiated Connection.Config.FrameSize, so an extreme declared size drives a correspondingly huge Go heap allocation before any body bytes are received, exhausting memory and terminating the process. The exploitation model is broker-attacks-its-clients rather than exploitation by an arbitrary network attacker (CVSS 4.0 8.9 with AT:P, and the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning the victim application must connect to a broker that is hostile, subverted, or on a path an attacker can tamper with; no client credentials or unusual configuration are needed, and a FrameSize of 0 ("unlimited") removes the cap entirely even after patching. There is no CISA KEV entry and no public exploit identified at time of analysis, but the upstream fix commit, test case, and 1.13.0 release are all public.
Denial of service in the RabbitMQ amqp091-go Go client for AMQP 0.9.1 (versions prior to 1.13.0) allows a malicious or compromised broker to advertise a FrameMax below the protocol's 4096-byte frameMinSize during connection negotiation, causing the client to fragment subsequent publications into an excessive number of frames and write operations, consuming CPU and stalling the client process or its host. The assessed vector carries PR:N, so no authentication is required on the client side, but exploitation is bounded by a trust-boundary prerequisite: the victim Go application must connect to a broker that the attacker controls or has compromised, and TLS with proper broker authentication prevents an unrelated network attacker from impersonating the broker. Impact is availability-only with no loss of confidentiality or integrity, and no public exploit code has been identified at time of analysis.
Crafted OSPFv3 packets can force an unexpected restart of the OSPFv3 routing agent on Arista EOS devices that have OSPFv3 configured, causing a transient loss of routing adjacencies and traffic disruption. The flaw is an availability-only denial of service (CWE-130 improper handling of length parameters) with no code execution, data disclosure, or persistence; no authentication is required (PR:N) and no user interaction is needed (UI:N), but exploitation depends on a preconditioned packet and, per our assessment, an attacker positioned on the same OSPFv3-participating link or adjacency domain rather than arbitrarily across the internet. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor has published Security Advisory 0173.
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.
Unauthenticated server-side request forgery in DataGear through 6.0.0 lets any remote attacker who can reach the web interface force the server to issue arbitrary HTTP requests - GET, POST, PUT, PATCH, or DELETE - to internal hosts and cloud metadata services via the /dataSet/preview/Http endpoint, returning the full response body to the caller. The endpoint is reachable without credentials (it is exempted by the SecurityConfigSupport allowlist), so the only prerequisite is network reachability to the DataGear instance, with impact maximized in cloud deployments where the link-local metadata service at 169.254.169.254 is reachable and can yield IAM credential theft. No public exploit code has been identified at time of analysis, the issue is not in CISA KEV, and no vendor-released patch has been identified.
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.
Advantech EKI-1242EIMS and EKI-1242IEIMS industrial gateways running firmware V1.06.01 expose their edgserver management protocol on TCP port 5058 without any authentication, allowing a remote unauthenticated attacker who can reach that port to invoke critical device-management functions such as network reconfiguration, reboot, reset, and firmware upgrade. The flaw is a CWE-306 missing authentication for critical function issue with CVSS 8.8 (v4.0) and an independently assessed CVSS 3.1 of 8.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H); the vector contains PR:N, confirming no credentials or user interaction are required. Impact is integrity and availability only - there is no confidentiality exposure - and there is no public exploit identified at time of analysis and no CISA KEV listing, so the practical risk is gated by whether the OT management segment is reachable from an untrusted network.
A use-after-free race in the arm64 KVM vGICv3 code path of the Linux kernel (vgic_v3_save_pending_tables) allows a locally authenticated guest with vCPU-level access to trigger a dangling-pointer dereference against host kernel memory. The flaw requires an arm64 KVM host configured with GICv3 LPI/ITS support, where a concurrent irqfd cached-injection plus a guest ITS DISCARD can free an LPI that the pending-table save loop still holds via a stale xarray iterator pointer; the practical outcome is a host-side crash/denial of service with limited integrity impact rather than a clean, reliable privilege escalation, and exploitation depends on a tight timing window (assessed AV:L/AC:H/PR:L, S:C, C:N/I:L/A:H). Vendor patches are available in Linux 6.18.51, 7.2.5, and 7.3-rc1; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
On LoongArch hosts running KVM, a memory-slot update that changes only flags (KVM_MR_FLAGS_ONLY, most notably toggling KVM_MEM_LOG_DIRTY_PAGES for live migration) zeroes the slot's architecture-specific flags, so a slot previously marked KVM_MEM_HUGEPAGE_INCAPABLE because of a GPA/HVA offset mismatch can subsequently be mapped with PMD-sized entries; because the mapping path aligns the guest frame number and host page frame number independently, the guest can read or write the wrong host pages, giving a local attacker with access to the KVM VM file descriptor both confidentiality and integrity impact on the host (CVSS 8.8 vendor score, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). The independent assessment rates the attack complexity higher (AC:H) because exploitation requires a misaligned memslot plus a flags-only update, typically during live migration, and does not manifest for a static guest with aligned memslots; only the LoongArch architecture is affected. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, though the tags classify the outcome as information disclosure and the successful corruption path is a memory-safety violation with high integrity impact.
Out-of-bounds kernel memory corruption in the Linux kernel's LoongArch KVM EIOINTC interrupt-routing code allows a local attacker who holds a VM file descriptor to read and write memory beyond the loongarch_eiointc allocation. The MSI data field supplied by userspace through KVM_SET_GSI_ROUTING (irqfd/KVM_IRQ_LINE) or KVM_SIGNAL_MSI is passed unchecked into eiointc_set_irq() and used as an IRQ index against 256-bit bitmaps and the sw_coremap[]/coreisr/sw_coreisr arrays, so any value of 256 or greater triggers deterministic, fully attacker-controlled out-of-bounds accesses with scope change from the guest process into kernel memory (CVSS 3.1 8.8, AV:L/PR:L/S:C). Exploitation is confined to LoongArch hosts running KVM and requires local access to the KVM interfaces; the DMSINTC path is unaffected because it decodes and masks the vector from the address. No public exploit code has been identified and the flaw is not confirmed actively exploited (not in CISA KEV), and vendor patches are available in the stable kernel commits referenced by the advisory.
An out-of-bounds write in the Linux kernel's HDMI-CEC driver for the Extron DA HD 4K Plus adapter (media: cec: extron-da-hd-4k-plus) lets a malicious or malfunctioning CEC device overflow the fixed-size msg.msg[] buffer, crashing the kernel and potentially corrupting kernel memory. Only hosts that have the extron-da-hd-4k-plus driver built and bound to an actual Extron DA HD 4K Plus CEC adapter are affected, and the malformed CEC message must arrive over the physically or adjacently attached CEC/serial link - there is no remote, over-the-network attack path against a default configuration. No public exploit code or in-the-wild exploitation has been identified at time of analysis, and the vendor's CVSS 8.8 (AV:A/AC:L/PR:N/UI:N/C:H/I:H/A:H) materially overstates real-world risk; our independent assessment is AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H, since the hardware is rare, the input channel is adjacent-only, and reliable escalation beyond a kernel crash is not demonstrated.
Repeated command aborts in the Linux kernel's qla2xxx (QLogic Fibre Channel) driver can reinitialize an already-queued work item, corrupting workqueue list state and leading to host crashes, hangs, or a looping worker - a denial-of-service condition on systems using NVMe over Fibre Channel. Affected code exists from the introduction commit e473b3074104ee09227cfbba5f872e3ea15dd280 (reported as Linux 4.17) onward, and fixes are available in stable releases 6.6.157, 6.12.110, 6.18.51, 7.2.5 and 7.3-rc1. No public exploit code has been identified at time of analysis, and the bug is a driver-internal timing race rather than an attacker-invokable primitive: triggering requires a host with a qla2xxx HBA actively handling NVMe-FC FCP or LS I/O where two aborts for the same command race (for example, concurrent transport teardown and a timeout-driven abort), so our assessment rates it substantially lower than the vendor's headline CVSS of 8.8 (AV:A/PR:N) - a local, high-complexity race with no confidentiality impact.
Wild-pointer dereference in the Linux kernel's qla2xxx QLogic Fibre Channel HBA driver lets an unexpected STATUS_TYPE completion IOCB reach a SCSI-only fast path, where the srb union is reinterpreted so sp->u.scmd.cmd reads as a non-NULL garbage pointer and is dereferenced. Only hosts running the qla2xxx driver with a physical QLogic FC HBA are exposed, and only when the adapter firmware or FC fabric delivers a mis-typed status IOCB that coincides with a live non-SCSI outstanding handle; the assessed vector is CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H, so the realistic outcome is a kernel crash rather than reliable code execution. No public exploit code or confirmed active exploitation has been identified at time of analysis, and vendor patches are available for all maintained stable branches.
Concurrent host_map btree corruption can occur in the Linux kernel's qla2xxx QLogic Fibre Channel driver because the format-1 branch of qla24xx_report_id_acquisition() releases vport_slock before invoking qla_update_host_map()/qla_update_vp_map(), which mutates ha->host_map without the serialization the function contract requires. Only systems running the qla2xxx driver with a QLogic FC HBA and NPIV virtual ports configured (a privileged local configuration) exercise this code path, and triggering it depends on winning a narrow, non-deterministic timing race against another host_map update. The result is kernel-internal data-structure corruption rather than direct data theft; no public exploit code has been identified and the issue is not confirmed as actively exploited (no CISA KEV).
Stale GPU TLB entries in the Linux kernel's AMD KFD (amdkfd) driver let in-flight DMA descriptors from already-unmapped MES-scheduled queues continue reading or writing memory that has been freed or migrated, producing page faults and hung compute queues. The flaw affects AMD GPU/APU systems running KFD/ROCm compute through the MES firmware scheduler path rather than the HWS path (which invalidates the TLB automatically), and was reproduced on gfx1151 (Strix Point) with XNACK mode 1 enabled during SVM page-migration workloads such as KFDSVMRangeTest.MultiThreadMigrationTest. It is a local, timing-sensitive race requiring a GPU-authorized local user, per our assessment triggers only during MES queue eviction (evict_process_queues_cpsch) or debug/CRIU queue suspension (suspend_queues) concurrent with SVM page migration; no public exploit identified at time of analysis, and it is not listed in CISA KEV. Vendor-released patches (Linux 6.18.51, 7.2.5, and 7.3-rc2) add the missing kfd_flush_tlb() calls.
A mismatched DMA unmap size in the nouveau DRM driver's device-private memory (dmem) migration path causes the kernel to unmap only PAGE_SIZE instead of the full compound-folio mapping size when device-private transparent huge pages (THP) are migrated. On affected systems running the open-source nouveau driver with dmem THP migration in use, an authenticated local attacker able to drive GPU device-memory migration workloads can repeatedly trigger the nouveau_dmem_migrate_to_ram() success path or the nouveau_dmem_migrate_copy_one() copy-error path, gradually leaking residual IOMMU/IOVA mappings for order>0 folios. No public exploit code exists and the issue is not confirmed as actively exploited (not in CISA KEV); EPSS and KEV signals are absent, and our independent assessment scores this as a low-impact, local-only mapping leak (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) rather than the 8.8 vendor vector, which overstates confidentiality, integrity, and scope impact.
Command injection in Pepperl+Fuchs ICE2/ICE3 and Phoenix Contact IOL MA8 series IO-Link Master devices allows a low-privileged remote attacker to execute arbitrary OS commands with root privileges by sending a crafted GET request to the /api/status/data REST endpoint. Three separate CERTVDE coordinated advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the same vulnerable firmware stack is shared across multiple industrial automation vendors, broadening the effective attack surface beyond any single manufacturer. No public exploit code or active exploitation has been identified at time of analysis.
Command injection via a PHP web management endpoint on Pepperl+Fuchs ICE2/ICE3 series IO-Link Masters and Phoenix Contact IOL_MA8_PN_DI8 allows an authenticated operator-level attacker to execute arbitrary OS commands with root privileges on the device. The vulnerable endpoint, `/index.php/attached_devices_tab/ajax_remove_uploaded_iodd_files`, passes user-supplied filenames to an underlying OS command without sanitization, enabling full device compromise. No public exploit code or KEV listing has been identified at time of analysis, but the low attack complexity and network accessibility make this a serious risk in OT/ICS environments.
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.
Command injection via the PHP-based IODD parameter save endpoint on Pepperl+Fuchs ICE2/ICE3 series IO-Link masters and OEM-equivalent devices allows an authenticated operator-level attacker to execute arbitrary OS commands with root privileges on the device. Affected hardware includes multiple ICE2 and ICE3 form-factor variants from Pepperl+Fuchs and the Phoenix Contact IOL MA8 PN DI8, with additional OEM-labeled variants covered under three separate CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028). No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Command injection in Pepperl+Fuchs ICE2/ICE3 IO-Link Master devices (and OEM variants from Phoenix Contact and others) allows a low-privileged authenticated remote attacker to execute arbitrary OS commands with root privileges via the PHP-based /index.php/ajax/parameterManage endpoint. The flaw is tracked across three CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028), indicating the vulnerable firmware is shared across multiple vendor rebrand families. No public exploit has been identified and the vulnerability is not listed in CISA KEV at time of analysis.
Command injection via the Field_Shadow_Password class in Pepperl+Fuchs ICE2/ICE3 IO-Link master devices and Phoenix Contact IOL_MA8_PN_DI8 allows a network-authenticated attacker holding only operator-level credentials to inject OS commands that execute with root privileges on the device. The vulnerability (CWE-78) is exploitable without user interaction against a low-privileged account, resulting in full confidentiality, integrity, and availability compromise of the affected industrial device. No public exploit code or CISA KEV listing has been identified at time of analysis; three coordinated CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) cover multiple vendor families sharing the same underlying platform.
Command injection in Pepperl+Fuchs ICE2/ICE3 series and Phoenix Contact IOL_MA8 IO-Link master devices enables an authenticated low-privileged attacker to execute arbitrary OS commands as root via the /index.php/attached_devices_tab/do_upload web management endpoint. The vulnerability (CWE-78) is exploitable remotely without user interaction using only operator-level credentials, yielding full device compromise including confidentiality, integrity, and availability of the industrial gateway. No public exploit code or CISA KEV listing has been identified at time of analysis, though three separate CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate coordinated multi-vendor disclosure.
Command injection in Pepperl+Fuchs ICE2/ICE3 IO-Link Master devices and OEM equivalents allows a low-privileged authenticated attacker to execute arbitrary OS commands as root via the /index.php/ajax/get_iodd_port_info PHP endpoint. Affected hardware spans multiple ICE2 and ICE3 form factors (G65L, K45P, K45S housings) as well as Phoenix Contact IOL MA8 and additional OEM-branded variants sharing the same firmware. No public exploit code has been identified at time of analysis, but the low attack complexity and high impact make this a credible priority in any industrial network where these devices are reachable.
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.
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.
Improper output encoding in the RabbitMQ amqp091-go Go client before 1.13.0 lets an attacker who can influence a TLS asset path value (CertFile, KeyFile, CACertFile, or ServerName) inject or overwrite AMQPS connection options whenever an application serializes a URI with URI.String() and later reparses it with ParseURI(). Because the values are concatenated into the query string without url.Values encoding, embedded '&' and '=' delimiters split into extra parameters that can redirect the client to different - but still pre-existing - local certificate, key, or CA files, corrupting connection configuration. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the vendor fix is version 1.13.0, and the practical risk is well below the headline 8.7 CVSS 4.0 score because exploitation needs a specific serialize-then-reparse code path plus attacker-influenceable path data.
Passive interception of the cleartext edgserver management protocol on Advantech EKI-1242EIMS and EKI-1242IEIMS devices running firmware V1.06.01 allows any observer positioned on the same network segment to recover sensitive device identity and network metadata as it traverses the wire. The vulnerability is unauthenticated and requires no user interaction (CVSS 4.0 vector AV:A/AC:L/AT:N/PR:N/UI:N), but our independent assessment scopes the real-world impact to confidentiality only (CVSS 3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) because a purely passive observer cannot alter or disrupt device behavior - the CVSS 4.0 base score of 8.7 reflects the vector's asserted high integrity and availability impact, which is not supported by the exploitation conditions. No public exploit code and no CISA KEV listing were identified at time of analysis, and the primary limiting factor is the requirement for network adjacency (the protocol is not remotely routable).
Authenticated non-guest users of Curiosity Workspace can escalate their privileges to administrator within an existing access group without an invitation or approval, as reported in CVE-2026-88817. The vendor rates this as high severity (CVSS 4.0 score 8.7), and our independent assessment confirms the impact is limited to the targeted access group-it does not grant application-wide administrator rights or root access to the host. No public exploit has been identified at the time of analysis, and a vendor advisory is available with potential remediation guidance.
Authentication bypass in the WNC T-Mobile 5G Box IDU router lets an attacker on the adjacent network reach the portal.cgi administration interface and log in without credentials by setting the sessionid cookie to a directory entry such as '.' or '..' that always exists under /tmp/login_user. The flaw affects firmware versions before 1.1.0.651412 and requires no authentication, no user interaction, and no non-default configuration - only network adjacency to the device (LAN or Wi-Fi side), since the assessed vector is AV:A. Impact is total: full read/write/execute control of the administrative panel, which is why the score is high (CVSS 4.0 8.7; assessed CVSS 3.1 8.7, C:H/I:H/A:H); no public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor firmware 1.1.0.651412 resolves the issue.
Unauthenticated elevated command execution is possible on Arista VeloCloud Edge appliances whenever High Availability is enabled, because the HA peer functions perform no caller verification (CWE-306). An attacker positioned on the private HA interconnect can invoke sensitive peer operations and obtain full confidentiality, integrity and availability impact on the Edge unit, reflected by a CVSS 4.0 base score of 8.7 (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H). No public exploit code has been identified at time of analysis, and the exploitable surface is adjacent-only - it is the HA interconnect segment rather than the routed internet, and units without HA configured are not affected.
Unauthenticated remote access to the configuration download function on XikeStor Layer3 switches (SKS8300-8T, SKS8300-12E2T2X, SKS8310-8X) running firmware below V1.04.B09 exposes full device configuration files to any network-reachable attacker. Recovered configurations contain network topology details and credentials, enabling attackers to authenticate to the switch itself or leverage it as a pivot point into the protected network segment it manages. Disclosed by JPCERT/CC (JVN#45281119); no public exploit code or active exploitation (CISA KEV) identified at time of analysis.