Delta DVP80ES3 CVE-2026-12575

Exploitation requires network reachability to the DVP80ES3's exposed service; per the CVSS vector AV:N/AC:L/PR:N/UI:N, no authentication and no user interaction are needed against the affected firmware, so any host that can reach the PLC's control/engineering port can attempt it. The truncated description ('DVP80ES3 with Improper Resource Shutdown or Release vulnerability') does not name a specific feature, protocol, or non-default setting as a precondition, so the concrete triggering interface is not fully specified in available data and should be confirmed via Delta-PCSA-2026-00009. The primary limiting factor is deployment context: PLCs are normally on isolated OT networks, so real-world reach depends on network segmentation rather than product-side authentication; impact is confined to availability (device crash/DoS), with no confidentiality or integrity effect per the vector.

The CVSS 3.1 base score is 7.5 (High) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating a network-reachable, low-complexity, unauthenticated attack whose sole impact is availability - a classic denial-of-service profile, not code execution or data theft. No EPSS score, KEV listing, or POC was provided, so there is no evidence of active or imminent exploitation; risk is driven by ease of triggering (no auth, low complexity) rather than observed attacker interest. A notable conflict exists in the data: the feed tag reads 'Information Disclosure,' yet the CVSS vector explicitly sets C:N (no confidentiality impact) and only A:H - the tag appears to be a generic or mislabeled classification and should not be treated as confirmed disclosure risk; verify against the Delta advisory. Real-world priority is context-dependent: for plant-network- or internet-exposed PLCs this is a meaningful operational-availability risk given the low bar to exploit, but for properly segmented OT networks the network vector is substantially mitigated.

An attacker with network access to the plant OT segment repeatedly opens connections to the DVP80ES3's exposed control service and sends requests that cause the firmware to leak or fail to release resources. After enough iterations the PLC exhausts available handles or memory and crashes or hangs, halting the industrial process it controls. No authentication or user interaction is required, and no public exploit code was identified in the provided data.