# CVE-2026-29128: IDC SFX2100 Satellite Receiver bgpd/ospfd/ripd/zebra Config Credential Disclosure via World-Readable Files

> Attackers can read world-readable configuration files to extract hardcoded plaintext credentials, enabling unauthorized access and privilege escalation on the satellite receiver.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-6gfq-hxv9-vhx9

## What is CVE-2026-29128?

CVE-2026-29128 is a high-severity vulnerability in International Datacasting Corporation SFX2100 Satellite Receiver, published on 5 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IDC SFX2100 Satellite Receiver firmware ships with multiple daemon configuration files for routing components (e.g., zebra, bgpd, ospfd, and ripd) that are owned by root but world-readable. The configuration files (e.g., zebra.conf, bgpd.conf, ospfd.conf, ripd.conf) contain hardcoded or otherwise insecure plaintext passwords (including “enable”/privileged-mode credentials). A remote actor is able to abuse the reuse/hardcoded nature of these credentials to further access other systems in the network, gain a foothold on the satellite receiver or potentially locally privilege escalate.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Datacast Sfx2100 Firmware.

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

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

## Is CVE-2026-29128 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29128 exists.

## Other vulnerabilities in International Datacasting Corporation SFX2100 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-29128 and fix it if it is affected.

What it is: CVE-2026-29128 is a high-severity vulnerability in International Datacasting Corporation SFX2100 Satellite Receiver, published on 5 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29128 exists.

Affected product: International Datacasting Corporation SFX2100 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-29128/ (Markdown: https://insights.sbomify.com/CVE-2026-29128/index.md)
```

## Sources

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

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