Aggregates CVE and security vulnerability intelligence across all smarsh-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Common weakness patterns include vendor risk path handling, with potential vendor impact file overwrite across vendor surface production workloads and vendor surface software deployment use cases.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-48931 | 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. | [email protected] | 3.2 | 0.08% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48930 | 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. | [email protected] | 2.8 | 0.07% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48929 | 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 date if discovered by an adversary. | [email protected] | 4.0 | 0.28% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48928 KEV | 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 HTTP would be included in this dump, as exploited in the wild in May 2025. | [email protected] | 4.0 | 0.37% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48927 KEV | 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. | [email protected] | 5.3 | 7.86% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48926 | The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers. | [email protected] | 4.3 | 0.21% | 2025-05-28 | 2026-06-17 |
| CVE-2025-48925 | 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. | [email protected] | 4.3 | 0.23% | 2025-05-28 | 2026-06-17 |
| CVE-2025-47730 | 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 logfile for the user and enRR8UVVywXYbFkqU#QDPRkO for the password. | [email protected] | 4.8 | 0.32% | 2025-05-08 | 2026-06-17 |