# CVE-2025-48927: TeleMessage TM SGNL insecure default configuration in Spring Boot Actuator

Source: https://junglewise.ai/threats/cve-2025-48927-telemessage-tm-sgnl-insecure-default-configuration-in-spring-boot  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-07-01. Updated: 2026-05-15  
License: CC BY 4.0 with a link back

CVE-2025-48927 · Severity: critical · CVSS 5.3 · Exploited in the wild · Published 2025-07-01

TeleMessage, a secure messaging service used for enterprise compliance, was found to have an insecurely configured server component. This flaw allowed unauthorized individuals to download a 'heap dump,' which is a snapshot of the application's memory that can contain sensitive information such as user messages, credentials, or encryption keys. This vulnerability has been exploited in the wild, potentially compromising the confidentiality of communications for affected organizations.

Technologies: [Telemessage TM SGNL](https://junglewise.ai/threats/technologies/tm-sgnl). Vendors: [Telemessage](https://junglewise.ai/threats/vendors/telemessage).

## Quick answers

**Is CVE-2025-48927 exploited in the wild?** Yes. CVE-2025-48927 is known to be exploited in the wild, first recorded on 1 July 2025. Treat it as urgent.

**How severe is CVE-2025-48927?** Critical severity, with a CVSS score of 5.3, published 1 July 2025.

**Which products and versions are affected?** Telemessage TM SGNL through 2025-05-05.

**Is there a fix for CVE-2025-48927?** 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-48927 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-48927?** 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

The TeleMessage service (TM SGNL) through 2025-05-05 was configured with an insecure default for the Spring Boot Actuator component. Specifically, the '/heapdump' URI was left exposed to the public internet without authentication (CWE-1188). An unauthenticated remote attacker can request this endpoint to download a full JVM heap dump. This snapshot of the application's memory can be analyzed offline to extract sensitive data, including session tokens, environment variables, and potentially decrypted message content. This vulnerability is confirmed to have been exploited in the wild.

## Affected products

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

## Timeline

- 2025-05-05: other: Vulnerability identified in service version through this date
- 2025-05-28: disclosed: CVE published and initial disclosure via media reports
- 2025-07-01: kev added: CISA added to Known Exploited Vulnerabilities catalog

## Related threats

- [TeleMessage TM SGNL core dump exposure in JSP application](https://junglewise.ai/threats/cve-2025-48928-telemessage-tm-sgnl-core-dump-exposure-in-jsp-application)
- [TeleMessage TM SGNL Hidden Functionality Vulnerability](https://junglewise.ai/threats/cve-2025-47729-telemessage-tm-sgnl-hidden-functionality-vulnerability)