VulnerabilityPublished 28 May 2025Updated 26 Feb 2026

CVE-2025-48928: TeleMessage service · Exposure of Core Dump File to an Unauthorized Control Sphere

Affects TeleMessage serviceSource CVE Database V5

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

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

4.0Medium

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.
EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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-48928 (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 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.

Impact

The primary impact of CVE-2025-48928 is the potential exposure of user passwords stored in heap memory, which can lead to unauthorized access if attackers gain local access to the system. This compromises confidentiality but does not affect data integrity or system availability. Organizations relying on TeleMessage services risk credential leakage, which could facilitate further attacks such as account takeover, lateral movement, or privilege escalation. The vulnerability is particularly concerning in environments where local access controls are weak or where multiple users share the same system. Since the passwords are transmitted over HTTP, the risk is compounded by insecure transmission channels. Although exploitation requires local access, the ease of attack complexity and lack of required privileges make it a viable threat in multi-tenant or shared hosting environments. The absence of known exploits in the wild suggests limited current exploitation but does not preclude future attacks.

Mitigation

To mitigate CVE-2025-48928, organizations should immediately upgrade or patch the TeleMessage service once a fix is available. In the absence of a patch, restrict local access to systems running the vulnerable TeleMessage service to trusted personnel only. Implement strict access controls and monitoring on servers hosting the application to detect unauthorized access attempts. Transition from HTTP to HTTPS to protect passwords during transmission and prevent interception. Review and sanitize application memory handling to avoid retaining sensitive data longer than necessary, including clearing heap memory after use. Employ runtime memory protection tools and consider application-level encryption for sensitive data in memory. Conduct regular security audits and penetration testing focused on memory exposure vulnerabilities. Additionally, enforce strong password policies and multi-factor authentication to reduce the impact of potential credential exposure.

CWE-528Exposure of Core Dump File to an Unauthorized Control Sphere (opens in a new tab)
Variant weakness
The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
System Configuration
Protect the core dump files from unauthorized access.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V12.5.1 (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:44 UTC

WeaknessesCWE-528

Technical details

References

Community reviews

Related threats