VulnerabilityPublished 4 Mar 2026

CVE-2026-28776: International Datacasting Corporation (IDC) IDC SFX2100 SuperFlex Satellite Receiver · Use of Hard-coded Credentials

Affects International Datacasting Corporation (IDC) IDC SFX2100 SuperFlex Satellite ReceiverSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
International Datacasting Corporation (IDC)IDC SFX2100 SuperFlex Satellite Receiver	Affected =SFX2100	Fixed in–

AI-suggested

Immediately isolate IDC SFX2100 devices from untrusted networks and restrict SSH access to trusted management networks only.
Disable SSH access entirely if it is not required for operational purposes.
Implement network-level controls such as firewall rules and VPNs to limit access to the devices.
Monitor network traffic and device logs for any unauthorized SSH connection attempts or unusual activity.
Engage with International Datacasting Corporation to obtain information on planned patches or firmware updates and apply them promptly once available.
Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect SSH brute force or unauthorized access attempts targeting these devices.
For critical environments, evaluate the feasibility of replacing affected hardware with more secure alternatives that do not contain hardcoded credentials.
Document and enforce strict operational procedures for device management, including regular audits of access controls and credentials.
If possible, implement compensating controls such as multi-factor authentication at the network gateway level to reduce risk exposure.
Educate operational staff about the risks associated with this vulnerability and the importance of adhering to mitigation protocols.

Description

International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver contains hardcoded credentials for the `monitor` account. A remote unauthenticated attacker can use these trivial, undocumented credentials to access the system via SSH. While initially dropped into a restricted shell, the attacker can trivially break out to achieve standard shell functionality.

Impact

The exploitation of this vulnerability allows an unauthenticated attacker to gain unauthorized SSH access to IDC SFX2100 devices, potentially leading to full device compromise. This can result in unauthorized disclosure or manipulation of satellite broadcast data, disruption of data distribution services, and potential use of the compromised device as a foothold within critical broadcast or communication networks. Organizations relying on these devices for satellite data transmission or reception could face operational disruptions, loss of data integrity, and exposure of sensitive broadcast content. The ability to bypass the restricted shell and obtain full shell access increases the risk of persistent compromise and lateral movement within the network. Given the specialized nature of the device, the impact is particularly severe for broadcasters, government agencies, and critical infrastructure operators using IDC equipment. The lack of available patches increases the window of exposure, and the remote, unauthenticated nature of the attack vector heightens the urgency for mitigation.

Summary

CVE-2026-28776 identifies a critical security flaw in the IDC SFX2100 SuperFlex Satellite Receiver, where hardcoded credentials for the 'monitor' account are embedded within the device's firmware or software. These credentials are undocumented and cannot be changed by the end user, allowing any remote attacker to connect via SSH without authentication. Upon login, the attacker initially lands in a restricted shell environment; however, this restriction can be trivially bypassed to gain full shell access, effectively providing complete control over the device. The vulnerability stems from CWE-798, the use of hardcoded credentials, which is a well-known security anti-pattern that severely undermines device security. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N) indicates that the attack requires no privileges, no user interaction, and can be executed remotely over the network with low attack complexity. The impact on confidentiality and integrity is low to limited due to the device's specialized function, but the scope is high because the attacker gains full shell access. The vulnerability is particularly concerning given the device's role in satellite data distribution, where compromise could lead to interception or manipulation of broadcast content. No patches or firmware updates have been released yet, and no exploits have been observed in the wild, but the risk remains significant due to the ease of exploitation and the critical nature of the device's function.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

abdulmhsblog.com/posts/sfx2100-vulns/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Mar 2026, 19:55 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats