Skip to content
CTI Academy Sponsor CTI Academy
MEDIUM · CVSS 5.3 CISA Known Exploited Vulnerability

CVE-2025-48927

TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability

TeleMessage TM SGNL

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.

CVSS
5.3
MEDIUM
EPSS
11.1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
28 May 2025
CWE-1188

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 1 July 2025. US federal agencies were required to remediate it by 22 July 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 11.1%, which is higher than 95.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Frequently asked questions

Is CVE-2025-48927 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-48927.

What does CVE-2025-48927 affect?

CVE-2025-48927 affects TeleMessage TM SGNL. 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.

How severe is CVE-2025-48927?

CVE-2025-48927 is rated MEDIUM with a CVSS base score of 5.3. EPSS puts the probability of exploitation in the next 30 days at 11.1%, higher than 95.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 July 2025.

How should organisations respond to CVE-2025-48927?

Apply the vendor patch for TeleMessage TM SGNL as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.