Quick answers
- Is CVE-2026-55728 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55728 being exploited in the wild.
- How severe is CVE-2026-55728?
- Informational severity, with a CVSS score of 3.8, published 24 July 2026.
- Which products and versions are affected?
- LOYTEC L-DALI through 8.4.16; LOYTEC L-GATE through 8.4.16; LOYTEC L-INX through 8.4.16; LOYTEC L-IOB through 8.4.16; and 4 more.
- Is there a fix for CVE-2026-55728?
- A patch was published on 2026-07-24: Fixed in firmware 8.4.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55728 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-55728?
- Check whether you run LOYTEC L-DALI, LOYTEC L-GATE, LOYTEC L-INX or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow (CWE-121) exists in the 'cmd_ipaddr_conflict' function within the '/usr/bin/ltsudo' SUID-root binary. The vulnerability is caused by the use of 'strcpy' to copy a user-supplied interface-name argument into a fixed 20-byte stack buffer without length validation. An attacker with 'superadmin' group privileges can exploit this locally to trigger a process abort or potentially achieve arbitrary code execution with root privileges. The issue affects multiple Loytec product lines on the LINX-A64 platform with firmware versions up to 8.4.16. A fix is available in firmware version 8.4.18.
Affected products
- Loytec LIP-ME201C through 8.4.16
- Loytec L-INX through 8.4.16
- Loytec L-GATE through 8.4.16
- Loytec L-ROC through 8.4.16
- Loytec L-IOB through 8.4.16
- Loytec L-DALI through 8.4.16
- Loytec L-VIS through 8.4.16
- Loytec L-PAD through 8.4.16
Timeline
- 2026-07-24: advisory
- 2026-07-24: disclosed
- 2026-07-24: patched: Fixed in firmware 8.4.18