Loytec LIP-ME20xC up to 8.4.16 /usr/bin/ltsudo cmd_ipaddr_conflict interface-name stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 2.35- |
Summary
A vulnerability, which was classified as very critical, was found in Loytec LIP-ME20xC, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD up to 8.4.16. The affected element is the function cmd_ipaddr_conflict of the file /usr/bin/ltsudo. Such manipulation of the argument interface-name leads to stack-based overflow.
This vulnerability is documented as CVE-2026-55728. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability, which was classified as very critical, has been found in Loytec LIP-ME20xC, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD up to 8.4.16. Affected by this issue is the function cmd_ipaddr_conflict of the file /usr/bin/ltsudo. The manipulation of the argument interface-name with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. CVE summarizes:
Stack-based Buffer Overflow (CWE-121) in `/usr/bin/ltsudo` `cmd_ipaddr_conflict` in Loytec LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD through 8.4.16 on LINX-A64 allows a `superadmin`-group attacker to trigger a SUID-root process abort or potentially elevate privileges via an overly long interface-name argument.
The advisory is shared for download at loytec.com. This vulnerability is handled as CVE-2026-55728 since 06/17/2026. The exploitation is known to be easy. The attack may be launched remotely. The exploitation needs additional levels of successful authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/24/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 9.1
VulDB Base Score: 9.1
VulDB Temp Score: 9.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/17/2026 CVE reserved07/24/2026 Advisory disclosed
07/24/2026 VulDB entry created
07/24/2026 VulDB entry last update
Sources
Advisory: loytec.comStatus: Not defined
CVE: CVE-2026-55728 (🔒)
GCVE (CVE): GCVE-0-2026-55728
GCVE (VulDB): GCVE-100-382916
Entry
Created: 07/24/2026 16:40Changes: 07/24/2026 16:40 (54)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.