CVE-2025-48928: TeleMessage TM SGNL core dump exposure in JSP application

CVE-2025-48928 · Severity: critical · CVSS 4 · Exploited in the wild · Published 2025-07-01

TeleMessage TM SGNL, a secure messaging service used for enterprise communications, contains a vulnerability that exposes sensitive memory contents. An attacker could access a 'core dump' file containing the heap memory of the application, which may include user passwords previously sent over the network. This flaw has been observed being exploited in the wild, potentially leading to unauthorized account access and the compromise of private communications.

Technologies: Telemessage TM SGNL. Vendors: Telemessage.

Quick answers

Is CVE-2025-48928 exploited in the wild?
Yes. CVE-2025-48928 is known to be exploited in the wild, first recorded on 1 July 2025. Treat it as urgent.
How severe is CVE-2025-48928?
Critical severity, with a CVSS score of 4, published 1 July 2025.
Which products and versions are affected?
Telemessage TM SGNL through 2025-05-05.
Is there a fix for CVE-2025-48928?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-48928 attacked?
It is attacked with local access, in a hosted service.
Am I affected by CVE-2025-48928?
Check whether you run Telemessage TM SGNL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

TeleMessage TM SGNL is a JSP-based application that suffers from an exposure of sensitive information via core dump files (CWE-528/CWE-552). The application's heap content, which is equivalent to a core dump, is accessible to unauthorized control spheres. This memory dump can contain plaintext passwords that were previously transmitted over HTTP. While the CVSS vector suggests local access (AV:L), the vulnerability has been confirmed as exploited in the wild as of May 2025. Organizations are advised to apply vendor-provided mitigations or discontinue use if patches are unavailable.

Affected products

  • TeleMessage (Smarsh) TM SGNL (TeleMessage) through 2025-05-05

Timeline

  • 2025-05-05: other: Vulnerability confirmed present in service through this date
  • 2025-05-28: disclosed: CVE assigned and initial details released
  • 2025-05-01: exploited: Exploited in the wild in May 2025
  • 2025-07-01: kev added: Added to CISA KEV catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.