Delta AS320T CVE-2026-1950

No special conditions - remote unauthenticated exploitation against default configurations of Delta AS320T devices. Attack requires only network connectivity to AS320T file processing interfaces, which may be exposed on management ports or web interfaces depending on deployment. No authentication, user interaction, or non-default configuration needed based on CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N. Attack complexity is low, indicating reliable exploitation without race conditions or environmental dependencies. Exploitation is limited only by network accessibility to the vulnerable filename processing functionality.

This represents a critical real-world risk for industrial control environments. The CVSS 9.8 score is fully justified by the attack characteristics: network-accessible (AV:N), low complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and complete compromise possible (C:H/I:H/A:H). While EPSS and KEV status are unavailable, the vendor acknowledgment and advisory publication confirm vulnerability legitimacy. The industrial automation context amplifies risk since AS320T devices likely operate in manufacturing, building automation, or process control environments where remote code execution could enable operational disruption, safety incidents, or supply chain attacks. No public exploit code is confirmed at time of analysis, but the straightforward nature of buffer overflow exploitation combined with network accessibility creates high weaponization potential. The vendor advisory covering four CVEs simultaneously (CVE-2026-1949 through 1952) suggests broader security posture concerns with this product line. Priority should be high for organizations with AS320T deployments, particularly those exposed to untrusted networks.

An attacker identifies an exposed Delta AS320T device through industrial control system reconnaissance scanning. They craft a network request to a file handling endpoint (upload, download, or configuration import) containing a filename exceeding expected buffer size with embedded shellcode. The unchecked filename triggers stack buffer overflow during processing, overwriting return addresses to redirect execution to attacker-controlled code, achieving remote code execution with device privileges to manipulate industrial processes or establish persistent access.