# CVE-2025-59452: Weak cryptography in YoLink API

> YoLink API uses weak MD5 hashing of non-secret data for endpoint derivation, allowing attackers to bypass security controls and access device endpoints.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-ph5v-r485-jfgw

## What is CVE-2025-59452?

CVE-2025-59452 is a medium-severity vulnerability in YoSmart YoLink API, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device's MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2025-59452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59452 is a medium-severity vulnerability in YoSmart YoLink API, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59452 in the wild and no public exploit code.

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

## Sources

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

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