Vendor scorecard
CISA lists 3 TeleMessage vulnerabilities as exploited in the wild, 0 of them added in the last 12 months (down from 3 in the 12 months before). 0 (0%) are known to be used in ransomware campaigns. For entries added in the last two years, the median time from CVE publication to the KEV listing was 34 days. Most affected: TM SGNL (3).
| Product | KEV entries |
|---|---|
| TM SGNL | 3 |
| CVE | Vulnerability | Added |
|---|---|---|
| CVE-2025-48928 | TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere VulnerabilityTM SGNL | |
| CVE-2025-48927 | TeleMessage TM SGNL Initialization of a Resource with an Insecure Default VulnerabilityTM SGNL | |
| CVE-2025-47729 | TeleMessage TM SGNL Hidden Functionality VulnerabilityTM SGNL |
Get an email when CISA adds the next TeleMessage CVE.
How to read this: CISA KEV lists vulnerabilities with reliable evidence of exploitation; a vendor with many entries is often one with a large, internet-facing install base, not necessarily worse engineering. "Publication → KEV" is the median number of days between the CVE's publication and its addition to KEV, for entries added in the last 24 months (3 entries); it is an upper bound on how long defenders had, since exploitation usually starts before the listing. Under NIS2 article 21(2)(d), supplier security is part of your risk management; this page is a starting point for that review. Compare vendors on the scorecard index.
We assess supplier security for NIS2 and DORA, from exploited-CVE history and patch response to contract clauses and evidence packs.
Get in touch →