CVE-2025-48930VulnerabilityPublished 28 May 2025Updated 1 Jul 2025

CVE-2025-48930: TeleMessage service · Cleartext Storage of Sensitive Information in Memory

Affects TeleMessage serviceSource CVE Database V5

Not known to be exploited · CVSS 2.8 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.8Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Changed
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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

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: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

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

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 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

Affected software

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

AI-suggested

Given the nature of this vulnerability, European organizations should implement the following specific mitigations: 1) Restrict and monitor local access to systems running the TeleMessage service, ensuring only authorized personnel have access. 2) Employ memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to make memory scraping more difficult. 3) Use endpoint detection and response (EDR) tools to detect unusual memory access patterns or attempts to read process memory. 4) Regularly audit and harden user privileges to minimize the risk of privilege escalation that could lead to memory exposure. 5) Isolate critical TeleMessage service instances in secure environments or virtual machines with strict access controls. 6) Engage with TeleMessage vendor support to obtain patches or updates as they become available and apply them promptly. 7) Implement encryption for sensitive data at rest and in transit within the TeleMessage ecosystem to reduce the impact if memory contents are exposed. 8) Conduct regular security training for staff to recognize and report suspicious activity that could lead to local compromise.

Description

The TeleMessage service through 2025-05-05 stores certain cleartext information in memory, even though memory content may be accessible to an adversary through various avenues.

Impact

For European organizations using the TeleMessage service, this vulnerability poses a limited but non-negligible risk. The primary concern is the potential exposure of sensitive information if an attacker gains local access to systems running the vulnerable TeleMessage service. This could occur through insider threats, compromised user accounts with local access, or chained exploits that escalate privileges to read memory. While the direct impact on confidentiality is low and there is no impact on integrity or availability, the exposure of sensitive data could lead to secondary attacks such as credential theft or unauthorized access to other systems. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and government, may face compliance risks if sensitive data is exposed. However, the requirement for local access and high attack complexity reduces the likelihood of widespread exploitation. The lack of known exploits in the wild further limits immediate risk, but organizations should remain vigilant and monitor for updates or patches from TeleMessage.

CWE-316Cleartext Storage of Sensitive Information in Memory (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in memory.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 04:41 UTC

WeaknessesCWE-316

Technical details

References

Community reviews

Related threats