# CVE-2025-57175: Hardcoded credentials in EtherHaul 8010

> Attackers can gain root access to Siklu EtherHaul 8010 devices using a static password, leading to full system compromise.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-7xx5-v8m5-xh6j

## What is CVE-2025-57175?

CVE-2025-57175 is a medium-severity vulnerability in Siklu EtherHaul 8010, published on 8 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Siklu EtherHaul 8010 siklu-uimage-nxp-enc-10_6_2-18707-ea552dc00b devices have a static root password.

Weakness: CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Ceragon Etherhaul-8010fx Firmware.

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

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

## Is CVE-2025-57175 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57175 is a medium-severity vulnerability in Siklu EtherHaul 8010, published on 8 Apr 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-2025-57175 in the wild and no public exploit code.

Affected product: Siklu EtherHaul 8010. 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-57175/ (Markdown: https://insights.sbomify.com/CVE-2025-57175/index.md)
```

## Sources

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

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