TE
Vendor
TeleMessage
13
CVEs
7
On KEV
0
New 30D
Products
TS5.3
TM SGNL
TeleMessage
3 CVEs3 on KEV0 new
SE9.8
service
TeleMessage
7 CVEs2 on KEV0 new
AB7.5
archiving backend
TeleMessage
2 CVEs1 on KEV0 new
TM4.9
Text Message Archiver
Telemessage
1 CVEs1 on KEV0 new
Recent CVEs
| CVE | Product | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2025-48931 | SE service TeleMessage | 5.5 | May 28 | The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort |
| CVE-2025-48927 In wildKEV | SE service TeleMessage | 5.3 | May 28 | TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability |
| CVE-2025-48930 | SE service TeleMessage | 5.3 | May 28 | The TeleMessage service through 2025-05-05 stores certain cleartext information in memory, even though memory content may be accessible to an adversary through various avenues |
| CVE-2025-48928 In wildKEV | SE service TeleMessage | 4.0 | May 28 | TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere Vulnerability |
| CVE-2025-48925 | SE service TeleMessage | 7.5 | May 28 | The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential |
| CVE-2025-48926 | SE service TeleMessage | 7.5 | May 28 | The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers |
| CVE-2025-48929 | SE service TeleMessage | 9.8 | May 28 | The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., not a token with a short expiration time) that can be reused at a later… |
| CVE-2025-47729 In wildKEV | AB archiving backend TeleMessage | 4.9 | May 8 | TeleMessage TM SGNL Hidden Functionality Vulnerability |
| CVE-2025-47730 | AB archiving backend TeleMessage | 7.5 | May 8 | The TeleMessage archiving backend through 2025-05-05 accepts API calls (to request an authentication token) from the TM SGNL (aka Archive Signal) app with the credentials of… |