CVE-2025-47729
TeleMessage TM SGNL Hidden Functionality Vulnerability
TeleMessage TM SGNL
The TeleMessage archiving backend through 2025-05-05 holds cleartext copies of messages from TM SGNL (aka Archive Signal) app users, which is different functionality than described in the TeleMessage "End-to-End encryption from the mobile phone through to the corporate archive" documentation, as exploited in the wild in May 2025.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 12 May 2025. US federal agencies were required to remediate it by 2 June 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.4%, which is higher than 39.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
Frequently asked questions
Is CVE-2025-47729 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-47729.
What does CVE-2025-47729 affect?
CVE-2025-47729 affects TeleMessage TM SGNL. The TeleMessage archiving backend through 2025-05-05 holds cleartext copies of messages from TM SGNL (aka Archive Signal) app users, which is different functionality than described in the TeleMessage "End-to-End encryption from the mobile phone through to the corporate archive" documentation, as exploited in the wild in May 2025.
How severe is CVE-2025-47729?
CVE-2025-47729 is rated LOW with a CVSS base score of 1.9. EPSS puts the probability of exploitation in the next 30 days at 0.4%, higher than 39.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 June 2025.
How should organisations respond to CVE-2025-47729?
Apply the vendor patch for TeleMessage TM SGNL as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.