# CVE-2025-59450: Hardcoded credentials in YoLink Smart Hub

> Attackers can extract network access credentials from unencrypted firmware, compromising IoT device security.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 6 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-pc64-x6mj-qcjf

## What is CVE-2025-59450?

CVE-2025-59450 is a medium-severity vulnerability in YoSmart YoLink Smart Hub, published on 6 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The YoSmart YoLink Smart Hub firmware 0382 is unencrypted, and data extracted from it can be used to determine network access credentials.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2025-59450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59450 is a medium-severity vulnerability in YoSmart YoLink Smart Hub, published on 6 Oct 2025. 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-59450 in the wild and no public exploit code.

Affected product: YoSmart YoLink Smart Hub. 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-59450/ (Markdown: https://insights.sbomify.com/CVE-2025-59450/index.md)
```

## Sources

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

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