Delta DVP80ES300T EUVD-2026-40911

Exploitation requires network reachability to the DVP80ES300T's communication interface and the ability to send a crafted request carrying an out-of-bounds array index value; per AV:N/AC:L/PR:N/UI:N no authentication, no user interaction, and no special product configuration are called out in the available data. The practical limiting factor is deployment topology rather than attack difficulty: PLCs are typically installed on isolated control networks, so an attacker must first reach that network segment. Impact is confined to availability (device crash/DoS) - there is no confirmed confidentiality or integrity effect - and exact affected firmware versions are not specified in the input, so which builds are actually exploitable remains unconfirmed.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) indicates a network-reachable, low-complexity, unauthenticated attack whose sole consequence is loss of availability - a clean DoS profile with no code-execution or data-disclosure claim. That said, there is a data conflict worth flagging: the intelligence tags label this 'Information Disclosure', yet the CVSS vector sets C:N (no confidentiality impact); the CVSS vector should be treated as authoritative and the tag verified against the Delta advisory. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so real-world exploitation likelihood cannot be quantified from the input. Priority should be weighted by operational context rather than raw score: a remote DoS against a PLC is a genuine safety/uptime concern in OT environments even without RCE, but PLCs are normally deployed on segmented control networks, which materially reduces the practical reachability implied by AV:N.

An attacker with network reachability to the PLC - for example after pivoting from an IT network into a poorly segmented control network - sends a crafted protocol request containing a manipulated index value that the firmware uses to access an internal array without bounds checking. The out-of-bounds access faults the firmware and halts the control program, stopping the monitored industrial process until the device is manually recovered. No authentication or user interaction is required (PR:N/UI:N), but no public exploit code has been identified at time of analysis.