BreakingTechEN

Cybersecurity

Four Flaws in iDirect Satellite Terminals: Exposed Data and Denial-of-Service Risk

CISA flags four vulnerabilities in ST Engineering iDirect iQ-Series terminals. Updating to version 4.5.3.0 is the recommended fix.

Radar

September 10, 2026 · 19:24

Translated from the Italian original: Italiano. This English edition was produced automatically and reviewed by our newsroom tools.

A low-angle view of communication dishes and antennas on a building against a clear blue sky.

ST Engineering iDirect satellite terminals from the iQ-Series family are at the center of an updated advisory from CISA, the U.S. cybersecurity agency. Four vulnerabilities, identified as CVE-2026-38056, CVE-2026-38057, CVE-2026-38058, and CVE-2026-38059, affect device management components and can lead to two significant consequences: unauthorized access to sensitive information and service disruption via denial of service.

The issue concerns equipment used in satellite communications, a domain where link availability and terminal identity are central operational elements. CISA places the product within a scope that spans communications, defense, energy, transportation, government facilities, and industrial infrastructure. This is not merely about the console security of an individual device: in certain configurations, a compromised or unavailable terminal can threaten communications continuity at remote sites and networks that rely on satellite connectivity.

Which products are affected

Advisory ICSA-26-183-01, revised on September 10, 2026, as Update A, identifies Evolution iQ-Series, 3315-Series, and 9-Series terminals running version 4.5.2.1 as affected. For these products, ST Engineering iDirect has made software version 4.5.3.0, or a subsequent release, available to address the reported flaws.

The advisory’s aggregate assessment yields a CVSS v3 score of 8.8 out of 10. While this indicates high severity, it must be evaluated alongside exposure conditions: the actual risk depends on whether the terminal’s administration interface and APIs are accessible from the attacker’s network. This is precisely one of the aspects emphasized by the mitigation recommendations: management interfaces should not be exposed to the Internet or left reachable from untrusted segments.

CISA's update outlines weaknesses falling into four categories: missing authentication for a critical function, cross-site request forgery (CSRF), improper authorization, and exposure of system information to unauthorized actors. The simultaneous presence of these issues suggests that the most critical area is the terminal's management surface—specifically, the services that collect device information and execute administrative operations.

Data that can aid an attack

The most concrete detail available in the advisory concerns CVE-2026-38059. On the iDirect iQ200 model, the REST endpoints /api/identity and /api/ are exposed without authentication. An actor with network access to the device can retrieve information such as the serial number, Device ID (DID), Terminal Private Key (TPK) identifier, MAC address, and the exact firmware version.

Not all of these elements carry the same weight, but together they build a technical profile that is extremely useful for mapping a network of terminals. DID and TPK, in particular, are used by the iDirect platform for authentication on the satellite network. According to the analysis reported by CISA, this exposure can facilitate both reconnaissance activities and terminal impersonation scenarios. The advisory assigns this single CVE a CVSS v3.1 score of 7.5 and describes an attack executable over the network with low complexity, requiring no privileges and no user interaction.

The operational takeaway is not just that an attacker can extract inventory details. Knowing the model, firmware, and identifiers enables better selection of follow-up techniques, pinpoints unpatched devices, and correlates information gathered across different networks. In distributed infrastructures, where the terminal is installed at a site far from IT or OT teams, even an apparently confined exposure can demand extensive verification.

From information theft to link continuity

The other three CVEs included in the advisory cover CSRF, missing authorization, and improper system information exposure. CISA warns that successful exploitation of these vulnerabilities could allow unauthorized access to device data or cause a denial of service condition. For operators, the second scenario warrants particular attention: a terminal outage does not necessarily impact the entire satellite network, but it can disrupt connectivity for a specific site, vehicle, facility, or backup link.

CISA also recommends monitoring for anomalous API activity and unexpected device reboots. These are practical indicators, as attacks on management systems can leave traces in the sequence of requests sent to APIs or in sudden changes to the device's state. This guidance, however, is no substitute for remediation: while monitoring can help detect suspicious signals, it does not eliminate the software flaw.

The presence of a CSRF vulnerability introduces an additional factor into the threat model. In such cases, a legitimate administrative session can become a conduit for unauthorized requests if the operator is tricked into interacting with attacker-crafted content. This is yet another reason to restrict terminal management to controlled networks, enforce robust authentication procedures, and, where possible, segregate administrative systems from general web browsing.

Update, isolate, verify exposure

The priority outlined by the vendor is upgrading the software to version 4.5.3.0 or later. Registered users can download the patches from the iDirect support portal. Before rolling out fixes, anyone managing a fleet of devices should inventory the deployed hardware and compare running versions against those listed in the advisory, including Evolution iQ-Series, 3315-Series, and 9-Series.

Alongside the update, CISA recommends mitigating measures that remain useful even after applying the patches:

  • allow access to management interfaces only from trusted networks, using VPNs or access control lists;
  • avoid exposing APIs and administrative services to the public web;
  • strengthen the authentication used for administrative functions;
  • monitor logs, API calls, and unexpected reboots, especially during the update phase and in the following weeks.

For organizations with operational constraints, updating a terminal at a remote site may require planning, maintenance windows, and a rollback plan. This does not reduce the urgency of the audit, but it makes it important to distinguish between directly exposed devices and those that are already segregated and accessible only via protected administrative paths. Indeed, even without Internet exposure, an overly broad internal network or poorly controlled remote access can provide the necessary entry point.

The advisory does not attribute the vulnerabilities to known exploitation campaigns and does not report confirmed compromises. This is an important detail to keep in mind to avoid treating a technical notification as an incident that has already occurred. At the same time, the combination of network access, potentially sensitive identification data, and the potential to cause downtime justifies a prompt response from administrators. The next practical step is to verify the installed release, shut down any unnecessary access to management interfaces, and schedule the migration to the patched version.

Sources

Read next