# CVE-2026-29120: Insecure, Hardcoded Root Password Stored in Anaconda Configuration File On IDC SFX2100 Satellite Receiver

> An attacker with local access can escalate privileges to root by cracking the hardcoded password hash stored in the configuration file.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-g8xm-r69x-48cj

## What is CVE-2026-29120?

CVE-2026-29120 is a critical vulnerability in International Datacasting Corporation IDC SFX2100 SuperFlex Satellite Receiver, published on 4 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The /root/anaconda-ks.cfg installation configuration file in International Datacasting Corporation (IDC) SFX Series(SFX2100) SuperFlex Satellite Receiver insecurely stores the hardcoded root password hash. The password itself is highly insecure and susceptible to offline dictionary attacks using the rockyou.txt wordlist. Because direct root SSH login is disabled, an attacker must first obtain low-privileged access to the system (e.g., via other vulnerabilities) to be able to log in as the root user. The password is hardcoded and so allows for an actor with local access on effected versions to escalate to root

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-29120?

It affects 1 product.


Products: Datacast Sfx2100 Firmware.

## How do I fix CVE-2026-29120?

No fix has been published for CVE-2026-29120 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29120 being exploited?

There is no known exploitation of CVE-2026-29120 in the wild and no public exploit code.

## Other vulnerabilities in International Datacasting Corporation IDC SFX2100 SuperFlex Satellite Receiver

- [CVE-2026-28775](https://insights.sbomify.com/CVE-2026-28775/): Unauthenticated RCE via SNMP Default Writable Community String (critical 10.0)
- [CVE-2026-28773](https://insights.sbomify.com/CVE-2026-28773/): Authenticated OS Command Injection via Ping Utility Leading to RCE as Root (critical 9.3)
- [CVE-2026-28774](https://insights.sbomify.com/CVE-2026-28774/): Authenticated OS Command Injection via Traceroute Utility leads to Root RCE (critical 9.3)
- [CVE-2026-29127](https://insights.sbomify.com/CVE-2026-29127/): Incorrect Permission Assignment(777) on `monitor` Users Home Directory Containing SUID Root Binaries in IDC SFX2100 (critical 9.2)
- [CVE-2026-28777](https://insights.sbomify.com/CVE-2026-28777/): Hardcoded and Insecure Credentials for "User" Local Account with SSH Access On IDC SFX2100 Satellite Receiver (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29120 and fix it if it is affected.

What it is: CVE-2026-29120 is a critical vulnerability in International Datacasting Corporation IDC SFX2100 SuperFlex Satellite Receiver, published on 4 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29120 in the wild and no public exploit code.

Affected product: International Datacasting Corporation IDC SFX2100 SuperFlex Satellite Receiver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29120/ (Markdown: https://insights.sbomify.com/CVE-2026-29120/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29120
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29120
- OSV: https://osv.dev/vulnerability/CVE-2026-29120

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29120/
Summaries are generated and may contain mistakes; the official description above is the record.