CVE-2025-48927: TeleMessage TM SGNL Initialization of a Resource with an Insecure Default
TeleMessage TM SGNL · listed in the CISA catalog of actively exploited vulnerabilities since 2025-07-01.
- CVSS v3.1 (CVE record)
- 5.3
- medium
- EPSS (exploit probability, 30 days)
- 12%
- higher than 96.2% of all CVEs
- Added to CISA KEV
- 2025-07-01
- US federal due date 2025-07-22
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2025-48927 explained
CVE-2025-48927 is an insecure default configuration in the TeleMessage service (TM SGNL). It configures Spring Boot Actuator with an exposed heap dump endpoint at a /heapdump URI. Attackers exploited it in the wild in May 2025, and CISA lists it as a known exploited vulnerability.
Impact
An unauthenticated remote attacker can reach the exposed heap dump endpoint over the network without user interaction. This can disclose information held in the service's memory. The CVSS vector rates the confidentiality impact as low, with no integrity or availability impact. CISA rates the technical impact as partial and the vulnerability as automatable, so it can be exploited at scale without manual steps. Attackers are known to use it.
Who is affected
The CVE record lists the TeleMessage service up to and including 2025-05-05 as affected (≤ 2025-05-05). The product is also referred to as TeleMessage TM SGNL. The CVE record names no fixed version. Check the vendor's instructions for the current status of the service.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
- It is recommended that mitigations be applied per vendor instructions if available. If these instructions cannot be located or if mitigations are unavailable, discontinue use of the product.
- nvd.nist.gov/vuln/detail/CVE-2025-48927
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- TeleMessage serviceAffectedFixed in
- ≤ 2025-05-05
not stated
| Product | Affected | Fixed in |
|---|---|---|
| TeleMessage service |
| not stated |
How to fix it
- The CVE record names no fixed version – check CISA's required action for updates and mitigations.
- CISA's deadline for US federal agencies: 2025-07-22 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply mitigations per TeleMessage's instructions as required by CISA.
- Follow applicable BOD 22-01 guidance if you use TeleMessage as a cloud service.
- Discontinue use of the product if mitigations are unavailable, as CISA's required action states.
- Review whether sensitive data handled by the service may have been exposed, and check for signs of compromise.
- Rotate credentials or secrets that may have been present in the service's memory.
The CVE record names no fixed version. Follow CISA's required action: apply mitigations per vendor instructions and follow BOD 22-01 guidance for cloud services. If no mitigations are available, discontinue use of the product. Monitor TeleMessage's guidance for updates on the service.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Weakness: CWE-1188 Initialization of a Resource with an Insecure Default
Questions about CVE-2025-48927
- Is CVE-2025-48927 being exploited?
- Yes. The description says it was exploited in the wild in May 2025. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-07-01, with a US federal due date of 2025-07-22.
- Why does a medium-severity issue need urgent action?
- Attackers are known to use it, it requires no authentication or user interaction, and CISA rates it as automatable. Exposed memory contents can include sensitive information.
- Is there a patched version?
- The CVE record names no fixed version. CISA requires applying vendor mitigations, following BOD 22-01 guidance for cloud services, or discontinuing use if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.