Inventory Moxa OnCell assets before treating CVE-2026-111461 as patched
A CVE record can create an assumption that a vendor patch exists somewhere and that the main task is deployment. CVE-2026-111461 breaks that assumption. The affected OnCell G3150A-LTE Series is end of life, and Moxa's mitigation is to keep SMS management disabled rather than to install a new firmware release for this line.
What is affected
Moxa's MPSA-269510 advisory assigns CVE-2026-111461 to an OS command injection flaw in the OnCell G3150A-LTE Series. The issue is CWE-78, the CVSS 4.0 score is 7.5, and the SMS upgrade argument reaches system() without escaping. The vendor says all firmware versions are affected and unauthenticated remote exploitation does not apply.
The advisory also covers CVE-2026-111459 and CVE-2026-111460. An inventory should preserve the exact CVE and product relationship instead of treating the whole advisory as a generic Moxa event.
Why inventory quality decides the response
An operator cannot disable SMS on an unknown gateway. An operator also cannot verify a management path when a device is represented only by a spreadsheet row with no network owner. The first evidence gap is usually completeness.
Build a list from procurement records, network discovery, firewall addresses, and site maintenance logs. Match each candidate against the OnCell G3150A-LTE Series. Record firmware, site, operational purpose, management address, account owner, SMS state, and replacement status. Mark duplicate addresses and devices behind NAT so that a count is not mistaken for a unique asset count.
Check assumption drift
Configuration records age quickly. A device that was installed with SMS disabled may have been changed during a field test or restored from a backup that enabled it. Verify the setting on the device or through an approved management channel.
The same applies to privileges. The CVE requires high privileges, so the account list is part of the inventory. Determine which users can perform SMS or upgrade operations and whether shared or stale accounts remain.
Use external fingerprints as a cross-check
ZoomEye returned 330 matches for app="Moxa OnCell". The exact CVE query returned 0. The product count is not proof of vulnerability, and the zero CVE result does not mean no affected assets exist. The comparison is useful because a product fingerprint can reveal a gateway that the internal inventory missed.
Do not place an external match directly into a victim list. Verify ownership, reachability, configuration, and evidence of compromise separately.
Set the remediation state
For each affected gateway, choose one of three documented states: retired, approved for controlled use with SMS disabled, or approved for controlled use with SMS enabled for a specific operational requirement. The last state needs a stronger exception with limited access, monitoring, and an end date.
Moxa's general recommendations support this approach. Limit communication to trusted networks, avoid direct internet exposure, disable unused services, enforce least privilege, and review logs. None of those controls should remain only in a policy document.
Know when the inventory is good enough
The inventory is ready for risk decisions when every known OnCell device has an owner and verified SMS state, management-network paths are documented, and every remains-in-service exception has an accountable approver. That is a higher bar than a scanner count, and a more useful one for an end-of-life command injection flaw.
Top comments (0)