# CVE-2025-58778: Hardcoded credentials in RG-EST300

> Attackers with knowledge of undocumented SSH credentials can access Ruijie RG-EST300 devices to read data, modify configurations, or cause denial of service.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-74q6-vjf5-fm72

## What is CVE-2025-58778?

CVE-2025-58778 is a high-severity vulnerability in Ruijie Networks Co., Ltd. RG-EST300, published on 16 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple versions of RG-EST300 provided by Ruijie Networks provide SSH server functionality. It is not documented in the manual, and enabled in the initial configuration. Anyone with the knowledge of the related credentials can log in to the affected device, leading to information disclosure, altering the system configurations, or causing a denial of service (DoS) condition.

Weakness: CWE-912 (Hidden Functionality)

## Which versions are affected by CVE-2025-58778?


## How do I fix CVE-2025-58778?

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

## Is CVE-2025-58778 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58778 and fix it if it is affected.

What it is: CVE-2025-58778 is a high-severity vulnerability in Ruijie Networks Co., Ltd. RG-EST300, published on 16 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58778 in the wild and no public exploit code.

Affected product: Ruijie Networks Co., Ltd. RG-EST300. 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-2025-58778/ (Markdown: https://insights.sbomify.com/CVE-2025-58778/index.md)
```

## Sources

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

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