Incorrect authorization in YoSmart YoLink MQTT broker
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-59449
- 2026-10-03 Alias added: GHSA-mrg6-25pv-x3g8
References
More YoSmart vulnerabilities
- TI-2025-36997 The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a… CVSS 3.1MEDIUM 5.8
- TI-2025-36993 Cleartext transmission of sensitive information in YoSmart YoLink ecosystem CVSS 3.1MEDIUM 4.7
- TI-2025-36995 Cleartext storage of sensitive information in YoSmart YoLink Smart Hub CVSS 3.1MEDIUM 4.3
- TI-2025-36996 The YoSmart YoLink application through 2025-10-02 has session tokens with unexpectedly long lifetimes. CVSS 3.1LOW 3.5
- TI-2025-36992 The YoSmart YoLink Smart Hub device 0382 exposes a UART debug interface. CVSS 3.1LOW 2.2
Sources
- CVE-2025-59449 · CVE Program
- CVE-2025-59449 · NVD
- FIRST EPSS
- GHSA-mrg6-25pv-x3g8 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences