VulnerabilityPublished 26 Aug 2025Updated 27 Aug 2025

CVE-2025-55443: Telpo MDM · Cleartext Storage of Sensitive Information

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% 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:H/I:N/A:H

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Aug 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 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

AI-suggested

European organizations should immediately audit their use of Telpo MDM and identify devices running vulnerable versions (1.4.6 through 1.4.9). Since no official patches are currently linked, organizations should implement compensating controls: 1) Restrict access to devices’ external storage by enforcing strict app permissions and using mobile device security policies to prevent unauthorized apps from reading log files. 2) Physically secure devices to prevent unauthorized access to external storage. 3) Monitor network traffic for unusual MQTT connections or administrative access attempts to the MDM platform. 4) Rotate administrator credentials and MQTT server credentials if possible, especially if there is suspicion of compromise. 5) Consider isolating the MQTT server and MDM platform behind strong network segmentation and access controls to limit exposure. 6) Engage with Telpo for updates or patches and plan for timely deployment once available. 7) Educate IT and security teams about the risks of storing sensitive information in plaintext and review logging practices to avoid similar issues. 8) Implement endpoint detection and response (EDR) solutions on managed devices to detect anomalous activities such as unauthorized factory resets or software installations.

Description

Telpo MDM 1.4.6 thru 1.4.9 for Android contains sensitive administrator credentials and MQTT server connection details (IP/port) that are stored in plaintext within log files on the device's external storage. This allows attackers with access to these logs to: 1. Authenticate to the MDM web platform to execute administrative operations (device shutdown/factory reset/software installation); 2. Connect to the MQTT server to intercept/publish device data.

Impact

For European organizations using Telpo MDM versions 1.4.6 to 1.4.9 on Android devices, this vulnerability poses a significant risk. Unauthorized access to administrator credentials can lead to full compromise of the MDM platform, allowing attackers to control managed devices remotely. This could result in widespread device shutdowns, factory resets causing data loss, or unauthorized software installations that may introduce malware or backdoors. The interception and manipulation of MQTT communications can lead to data breaches, loss of sensitive information, and disruption of device operations. Given that MDM platforms are often used to manage critical enterprise mobile assets, this vulnerability could disrupt business continuity, violate data protection regulations such as GDPR, and damage organizational reputation. The lack of required privileges or user interaction makes exploitation easier, increasing the likelihood of attacks if devices are physically or remotely accessible. The impact on availability and confidentiality is high, which is particularly concerning for sectors relying on mobile device fleets, including logistics, retail, healthcare, and public services across Europe.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
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)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/raiji1n/a2ce5dd46c312e3bd38b9b2446b95860 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Sep 2025, 01:12 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats