Actively exploited vulnerability

TeleMessage TM SGNL: memory corruption flaw under attack

CVE-2025-48928 · TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere Vulnerability

Business software4.0 medium

What is affected

TeleMessage TM SGNL is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

TeleMessage TM SGNL contains an exposure of core dump file to an unauthorized control sphere Vulnerability. This vulnerability 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 HTTP would be included in this dump.

CISA's description

What an attacker can do

This is a memory corruption flaw. It lets an attacker corrupt the program's memory by feeding it specially crafted content: a web page, a file or a network message. The result ranges from a crash to the attacker running their own code.

How it is reached
Needs access to the device or a file opened on it
Access the attacker needs
No account needed
Does the victim have to do something?
No, works without the victim doing anything

What to do

  1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
  2. If you administer TeleMessage TM SGNL at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
  3. If the product is past its support date and no fix exists, take it off the internet or retire it.

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

Action required by CISA for US federal agencies

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on July 1, 2025, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by July 22, 2025, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 0.6% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 44% of all scored vulnerabilities.

Its CVSS severity score is 4.0 out of 10 (medium), as recorded in the US National Vulnerability Database.

Technical description

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 HTTP would be included in this dump, as exploited in the wild in May 2025.

NIST National Vulnerability Database
5,442 members already hereReading, writing, commenting and voting. 0 verified · 167 joined this year