Smarsh provides enterprise communication archival and compliance platforms, with its vulnerability footprint concentrating in the TeleMessage product line. Vulnerabilities affecting the vendor skew toward critical severity and have an elevated tendency toward confirmed in-the-wild exploitation; the recurring weakness classes—including authentication bypass, cleartext storage of sensitive data, core dump exposure, and insecure defaults—reflect the challenges of securing access to archived communications and system state. Defenders should treat this vendor's advisories as high-priority given the sensitive nature of archived messaging data and the durable patterns around credential and information disclosure; current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Smarsh over time
Signals from CVEs in this vendor 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 |
Signals from CVEs in this vendor scope (8 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Smarsh.
Media articles that mention a CVE ID that affects a product developed by Smarsh — matched by CVE ID, not by vendor name.