CVE-2025-48927: TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability

Published May 28, 2025
·
Updated

TeleMessage TM SGNL contains an initialization of a resource with an insecure default vulnerability. This vulnerability relies on how the Spring Boot Actuator is configured with an exposed heap dump endpoint at a /heapdump URI.

Affected Software

4 affected components
TeleMessage TeleMessage service<=2025-05-05
Pivotal Spring Boot Actuator
TeleMessage TM SGNL
Smarsh TeleMessage

Remediation

Information

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Event History

May 28, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Jul 1, 2025
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Jul 2, 2025
News Published
via The Register·08:47 PM
News Published
via The Register·08:52 PM
Jul 18, 2025
News Published
via BleepingComputer·03:06 PM
News Published
via BleepingComputer·03:07 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-48927?

CVE-2025-48927 is considered a critical vulnerability due to exposed sensitive data through the heap dump endpoint.

2

How do I fix CVE-2025-48927?

To fix CVE-2025-48927, ensure that the Spring Boot Actuator's heap dump endpoint is disabled or properly secured.

3

What systems are affected by CVE-2025-48927?

CVE-2025-48927 affects the TeleMessage service versions up to and including 2025-05-05 that use Spring Boot Actuator.

4

What are the potential impacts of exploiting CVE-2025-48927?

Exploitation of CVE-2025-48927 can lead to unauthorized access to sensitive application data including the memory state of the application.

5

When was CVE-2025-48927 first exploited?

CVE-2025-48927 was first exploited in the wild in May 2025.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203