CVE-2025-47729
Telemessage Text Message Archiver ≤ 2025-05-05
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-47729 is a low-severity Hidden Functionality (CWE-912) vulnerability in Telemessage Text Message Archiver. Its CVSS base score is 1.9 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked at the 35th percentile by exploit likelihood (below the median); CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability in CVE-2025-47729 affects the TeleMessage archiving backend through 2025-05-05, which stores cleartext copies of messages sent by users of the TM SGNL (Archive Signal) mobile application. This behavior contradicts the product's documentation claiming end-to-end encryption from the device through to the corporate archive. The issue is tracked under CWE-912 and carries a low CVSS 3.1 score of 1.9 due to its local attack vector, high attack complexity, and requirement for high privileges.
An attacker with access to the backend server or its storage can read message contents that should have remained encrypted. Exploitation requires compromising or having authorized access to the archiving infrastructure rather than targeting end-user devices directly, allowing disclosure of archived communications that were expected to be protected.
Public references indicate the flaw was exploited in the wild in May 2025, prompting TeleMessage to investigate and ultimately cease operations for the affected service. The vulnerability has been added to the CISA Known Exploited Vulnerabilities catalog, and reporting links the product to high-profile users including U.S. government officials relying on the Signal-compatible client.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-14003
Vulnerability Data
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,…
more
as exploited in the wild in May 2025.
- CWE(s)
- KEV Date Added
- 12 May 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.