Telemessage
Vendor:
First CVE: May 8, 2025 · Active for 1 year
8
Total CVEs
More Total CVEs than 85% of tracked products
8.0
Avg CVEs / Year
Higher CVE frequency than 94% of tracked products
6.5
Avg CVSS
Higher Avg CVSS than 32% of tracked products
25.0%
KEV Rate
Higher KEV Rate than 98% of tracked products
Trends Over Time
The number and severity of CVEs published that impact Telemessage over time
Volume of CVEsAvg CVSS Base Score
First CVE
May 8, 2025
14 months ago
Most Recent CVE
May 28, 2025
422 days ago
CVE Severity & Scoring
Telemessage8 CVEs
50%
38%
13%
All CVEs352,294 CVEs
45%
40%
11%
MediumHighCritical
Attack Vector
Local2 (25.0%)
Network6 (75.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low8 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None8 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low1 (12.5%)
High0 (0.0%)
None7 (87.5%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (8 CVEs).
8 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2025-48927MEDIUM The TeleMessage service through 2025-05-05 configures Spring Boot Actuator with an exposed heap dump endpoint at a /heapdump URI, as exploited in the wild in May 2025. | May 28, 2025 | 5.3 | 62 | YES | NO |
CVE-2025-48928MEDIUM The TeleMessage service through 2025-05-05 is based on a JSP application in which the heap content is roughly equivalent to a "core dump" in which a password previously sent over H | May 28, 2025 | 4.0 | 52 | YES | NO |
CVE-2025-48929CRITICAL 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 | May 28, 2025 | 9.8 | 25 | NO | NO |
CVE-2025-48926HIGH The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers. | May 28, 2025 | 7.5 | 21 | NO | NO |
CVE-2025-48925HIGH 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. | May 28, 2025 | 7.5 | 20 | NO | NO |
CVE-2025-47730HIGH 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 logfil | May 8, 2025 | 7.5 | 20 | NO | NO |
CVE-2025-48931MEDIUM 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. | May 28, 2025 | 5.5 | 17 | NO | NO |
CVE-2025-48930MEDIUM 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. | May 28, 2025 | 5.3 | 16 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (8 CVEs).
CISA KEV
2 CVEs
25.0% of CVEs· 98th percentile
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (8 CVEs).
Media Mentions
Signals from CVEs in this product scope (8 CVEs).
Top CNAs Publishing CVEs For Telemessage
Top CWEs
Versions
No cataloged versions.