https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 04:54:37 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-261941 EUVD-2026-261941 https://cve.radiocsirt.org/vuln/euvd-2026-261941 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59452 <p>The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50.</p> <p>The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59452 https://cve.radiocsirt.org/vuln/ghsa-ph5v-r485-jfgw <p>The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50.</p> <p>The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50.</p> https://cve.radiocsirt.org/vuln/ghsa-ph5v-r485-jfgw https://cve.radiocsirt.org/vuln/icsa-26-013-03 <p>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&#39;s devices. The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50. Components of the YoSmart YoLink ecosystem through 2025-10-02 leverage unencrypted MQTT to communicate over the internet. An attacker with the ability to monitor network traffic could therefore obtain sensitive information or tamper with the traffic to control affected devices. This affects YoLink Mobile Application 1.40.41 and YoLink MQTT Broker. The YoSmart YoLink application through 2025-10-02 has session tokens with unexpectedly long lifetimes.</p> <p>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&#39;s devices. The YoSmart YoLink API through 2025-10-02 uses an endpoint URL that is derived from a device&#39;s MAC address along with an MD5 hash of non-secret information, such as a key that begins with cf50. Components of the YoSmart YoLink ecosystem through 2025-10-02 leverage unencrypted MQTT to communicate over the internet. An attacker with the ability to monitor network traffic could therefore obtain sensitive information or tamper with the traffic to control affected devices. This affects YoLink Mobile Application 1.40.41 and YoLink MQTT Broker. The YoSmart YoLink application through 2025-10-02 has session tokens with unexpectedly long lifetimes.</p> https://cve.radiocsirt.org/vuln/icsa-26-013-03