Read the docs
TI-2025-36997 Aliases CVE-2025-59452GHSA-ph5v-r485-jfgw

The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a…

Priority LOW 26CWE-340Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00439 38th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

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

VendorProductAffected versionsFixed inStatusSource
YoSmartYoLink APIup to 2025-10-02—No fix listedCNA
  • YoLink API VendorYoSmart Affected up to 2025-10-02 Fixed in — No fix listed CNA

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-59452
  2. 2026-10-03 Alias added: GHSA-ph5v-r485-jfgw

References

Other 4

  • TI-2025-36994 Incorrect authorization in YoSmart YoLink MQTT broker CVSS 3.1MEDIUM 4.9
  • 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

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences