CVERadar
MEDIUM · CVSS 3.1 4.9CISA KEV · added 2025-05-12EPSS 0.45% (p38)Threat level 40

CVE-2025-47729: TeleMessage TM SGNL Hidden Functionality Vulnerability

TeleMessage · TM SGNL · NVD published 2025-05-08 · posted 2025-05-12 · last modified 2026-06-17

What it is

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.

WeaknessCWE-912
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N (source: [email protected])
CISA due date2025-06-02 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2025-05-12 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2025-05-12. Source

Sources: CISA KEV.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • telemessage text message archiver: versions up to and including 2025-05-05 are affected; check the vendor advisory for the fixed release.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

    Detection Generic guidance

      Response checklist Generic guidance

      1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
      2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
      3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
      4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

      Sources