← gociux.comall vendors

Vendor scorecard

TeleMessage exploited vulnerabilities: 3 in CISA KEV, 0 in the last 12 months

Gociux · updated with each KEV addition · latest 1 Jul 2025

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).

3in CISA KEV
0last 12 months
0%ransomware-linked
34dpublication → KEV (median)

Exploited CVEs added per year

000030
202120222023202420252026

Most affected products

ProductKEV entries
TM SGNL3

Every exploited TeleMessage CVE

CVEVulnerabilityAdded
CVE-2025-48928TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere VulnerabilityTM SGNL1 Jul 2025
CVE-2025-48927TeleMessage TM SGNL Initialization of a Resource with an Insecure Default VulnerabilityTM SGNL1 Jul 2025
CVE-2025-47729TeleMessage TM SGNL Hidden Functionality VulnerabilityTM SGNL12 May 2025

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.

Reviewing TeleMessage as a supplier?

We assess supplier security for NIS2 and DORA, from exploited-CVE history and patch response to contract clauses and evidence packs.

Get in touch →