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

CVE-2025-48929: TeleMessage service · Insecure Storage of Sensitive Information

Affects TeleMessage serviceSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.0Medium

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
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: 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: 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: 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: 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

European organizations should implement the following specific mitigations: 1) Transition from long-lived credentials to short-lived, expiring tokens (e.g., OAuth tokens with limited lifetimes) to reduce the risk window if credentials are compromised. 2) Enforce secure storage mechanisms for authentication credentials, such as hardware security modules (HSMs) or encrypted vaults with strict access controls. 3) Implement multi-factor authentication (MFA) to add an additional layer of security beyond the compromised credentials. 4) Monitor authentication logs for unusual or repeated access patterns that may indicate credential misuse. 5) Rotate existing credentials proactively and invalidate any long-lived tokens currently in use. 6) Apply network segmentation and least privilege principles to limit the impact scope if credentials are compromised. 7) Engage with TeleMessage for updates or patches addressing this vulnerability and plan timely deployment once available. 8) Conduct regular security audits and penetration testing focused on authentication mechanisms to identify and remediate similar issues.

Description

The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., not a token with a short expiration time) that can be reused at a later date if discovered by an adversary.

Impact

For European organizations using the TeleMessage service, this vulnerability poses a risk of unauthorized access if an attacker obtains the long-lived credentials. Although the impact on confidentiality is rated low, the compromised credentials could allow adversaries to impersonate legitimate users or services, potentially leading to unauthorized information disclosure or misuse of the service. Since the vulnerability does not affect integrity or availability directly, the immediate operational disruption risk is low. However, the persistence of credentials increases the risk exposure duration, making it easier for attackers to exploit the vulnerability over time. Organizations handling sensitive communications or regulated data (e.g., under GDPR) could face compliance and reputational risks if unauthorized access leads to data breaches. The high attack complexity reduces the likelihood of widespread exploitation, but targeted attacks against high-value accounts remain a concern. The changed scope indicates that the vulnerability could allow access beyond the initially vulnerable component, potentially affecting interconnected systems or services within an organization's infrastructure.

Summary

CVE-2025-48929 is a medium-severity vulnerability classified under CWE-922, which pertains to the insecure storage of sensitive information. Specifically, the TeleMessage service, up to the version released on or before May 5, 2025, employs an authentication mechanism relying on long-lived credentials rather than short-lived tokens. These credentials do not expire quickly and can be reused multiple times. If an attacker manages to discover or extract these credentials, they can reuse them indefinitely to gain unauthorized access to the service. The vulnerability arises because the sensitive authentication tokens are stored or managed insecurely, increasing the risk of credential leakage. The CVSS 3.1 base score is 4.0, indicating a medium severity level, with the vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N. This means the attack can be performed remotely over the network (AV:N) but requires high attack complexity (AC:H), no privileges (PR:N), and no user interaction (UI:N). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality is low (C:L), with no impact on integrity or availability. No known exploits are currently reported in the wild, and no patches have been linked yet. The core issue is the insecure handling and storage of authentication credentials that do not expire promptly, increasing the window of opportunity for attackers to compromise accounts or services if credentials are leaked or stolen.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (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:42 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats