VulnerabilityPublished 28 May 2025Updated 26 Feb 2026

CVE-2025-48927: TeleMessage service · Insecure Default

Affects TeleMessage serviceSource CVE Database V5

Exploited in the wild · KEV due 22 Jul 2025 · 11% EPSS : apply the vendor's fix or mitigations to TeleMessage service now.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 22 Jul 2025 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 11.5% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 28 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 34 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE published
on cve.org
28 May 2025, t = 0
In Threat Radar
record ingested
28 May 202517:14 UTC, the same day as disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
1 Jul 2025, 34 days after disclosure
KEV remediation due
US federal deadline
22 Jul 2025, 55 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

nvd.nist.gov/vuln/detail/CVE-2025-48927 (opens in a new tab)

Affected software

Product	Affected	Fixed in
TeleMessage service	Affected =0	Fixed in–

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.

Impact

The primary impact of this vulnerability is the potential leakage of sensitive information contained within the heap dump, which could include user data, authentication tokens, encryption keys, or proprietary business logic. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach can facilitate subsequent attacks such as privilege escalation, data exfiltration, or targeted intrusion. Organizations relying on TeleMessage services for critical communications or data exchange could face reputational damage, regulatory penalties, and operational risks if sensitive information is exposed. The ease of exploitation (no authentication or user interaction required) increases the threat level, especially in environments where the actuator endpoints are accessible from untrusted networks. The scope includes all deployments of the affected TeleMessage service versions that have not disabled or secured the heap dump endpoint. Given the medium CVSS score, the impact is significant but not critical, emphasizing the need for timely mitigation to prevent information disclosure.

Mitigation

To mitigate CVE-2025-48927, organizations should immediately audit their TeleMessage service deployments to identify if the Spring Boot Actuator's /heapdump endpoint is exposed. Specific steps include: 1) Disable the heap dump endpoint if it is not required for operational purposes by setting management.endpoint.heapdump.enabled=false in the Spring Boot configuration. 2) Restrict access to actuator endpoints using network-level controls such as firewalls or VPNs to limit exposure to trusted administrators only. 3) Implement authentication and authorization mechanisms on actuator endpoints to prevent unauthenticated access. 4) Regularly update TeleMessage service and Spring Boot dependencies to incorporate security patches once available. 5) Monitor logs and network traffic for suspicious access attempts to actuator endpoints. 6) Conduct security reviews of default configurations in all Java-based services to avoid insecure resource initialization. These targeted mitigations go beyond generic advice by focusing on configuration hardening and access control specific to the heap dump endpoint.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 21:43 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats