Auditing Shared Cryptographic Keys on Moxa OnCell Devices
An audit for CVE-2026-111460 should answer a narrow question: can the organization show that each Moxa OnCell G3150A-LTE gateway no longer relies on the firmware's shared HTTPS private key and CA private key? Moxa says all firmware versions of the end-of-life series are affected and recommends a reset so the device regenerates its certificate and associated key material. A general assertion that the fleet was patched is not adequate evidence.
Establish the population
Start with a population that can be reconciled across procurement, network inventory and operations. Include model names, device identifiers, site ownership and management paths. Search results can suggest additional systems, but each candidate should be confirmed against an internal record.
For outside-in context, ZoomEye returned 330 matches for app="Moxa OnCell" on November 17, 2026, while vul.cve="CVE-2026-111460" returned 0. The first figure describes product fingerprints; the second describes CVE-indexed search results. Neither is a certificate audit, and neither establishes that an individual gateway is vulnerable or exploited.
Test the reset claim
For each device, collect the date and method of the documented reset. Confirm that the device certificate and associated key material were regenerated. The evidence can include a certificate identity, a reset work order, a configuration screenshot with sensitive fields removed, and a verification note from the operator.
Do not collect the private key itself. An audit needs enough evidence to show replacement occurred, not another copy of the secret. If old configuration backups contain key material, protect or dispose of them according to the organization's data-handling rules rather than circulating them as proof.
Review trust dependencies
A new device identity can break management workflows if peers still expect the old certificate. The audit should map the systems that trust the gateway and verify that they accept the new identity without being widened to trust broad certificate patterns.
Test the actual management path, not only the local login page. Record whether monitoring, remote support, certificate validation and configuration management still work. If an integration cannot be updated safely, document the compensating network restriction and the owner responsible for the remaining risk.
Verify scope and exceptions
Every firmware version is affected, and Moxa identifies the product as end of life. That means a successful key reset does not create a supported product lifecycle. The audit should keep a separate exception record for gateways that remain in service and mark a replacement commitment.
Use CVSS 4.0 7.7 and CWE-321 as context, not as a substitute for device evidence. The vendor's "under certain conditions" language, the lack of an in-the-wild exploitation claim in the reviewed sources, and the absence of a public trigger description should be represented accurately in the audit finding.
Reporting standard
A clear report separates three outcomes: product presence confirmed, key reset verified, and replacement completed. Counts should use those labels and avoid collapsing them into a single fixed total. That structure gives management a realistic view of what changed and what remains unsupported.
When a reset cannot be verified, leave the device open rather than guessing from a banner. When a device is retired, close the remediation item and retain the audit trail. This keeps the record defensible long after the immediate advisory cycle has passed.
Top comments (0)