# CVE-2025-59449: Missing authorization in YoLink MQTT broker

> Attackers can remotely control other users' YoLink devices by exploiting predictable IDs and missing authorization checks in the MQTT broker.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-mrg6-25pv-x3g8

## What is CVE-2025-59449?

CVE-2025-59449 is a medium-severity missing authorization vulnerability in YoSmart YoLink MQTT broker, published on 6 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The YoSmart YoLink MQTT broker through 2025-10-02 does not enforce sufficient authorization controls to prevent cross-account attacks, allowing an attacker to remotely operate affected devices if the attacker obtains the associated device IDs. Because YoLink device IDs are predictable, an attacker can exploit this to gain full control over any other YoLink user's devices.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-59449 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59449 is a medium-severity missing authorization vulnerability in YoSmart YoLink MQTT broker, published on 6 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59449 in the wild and no public exploit code.

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

## Sources

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

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