CVE-2025-65827VulnerabilityPublished 10 Dec 2025Updated 11 Dec 2025

CVE-2025-65827: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 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 17% 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:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: 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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 10 Dec 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

AI-suggested

European organizations should immediately enforce HTTPS-only communication in their mobile applications by disabling cleartext traffic permissions in app configurations (e.g., Android Network Security Configuration or iOS App Transport Security). All API endpoints must support and enforce TLS with strong cipher suites. Replace the use of MD5 hashing with modern, secure algorithms such as bcrypt, Argon2, or SHA-256 combined with salting to protect stored credentials and transmitted hashes. Implement secure token management practices, including short-lived tokens, token binding, and secure storage on the client side to prevent interception and replay. Conduct thorough security testing and code reviews to ensure no fallback to HTTP or weak cryptographic primitives exist. Educate users about the risks of using public Wi-Fi and encourage the use of VPNs for sensitive transactions. Monitor network traffic for anomalies indicative of man-in-the-middle attacks. Finally, prepare for rapid patch deployment once official fixes become available and maintain an incident response plan tailored to account compromise scenarios.

Description

The mobile application is configured to allow clear text traffic to all domains and communicates with an API server over HTTP. As a result, an adversary located "upstream" can intercept the traffic, inspect its contents, and modify the requests in transit. TThis may result in a total compromise of the user's account if the attacker intercepts a request with active authentication tokens or cracks the MD5 hash sent on login.

Impact

For European organizations, the impact of CVE-2025-65827 can be severe. The interception and modification of unencrypted API traffic can lead to unauthorized access to user accounts, resulting in data breaches, identity theft, and potential financial fraud. Organizations in sectors such as banking, e-commerce, healthcare, and government services that rely on mobile applications for user authentication and sensitive data exchange are particularly vulnerable. The compromise of authentication tokens can allow attackers to impersonate users, access confidential information, and perform unauthorized transactions. Additionally, the use of MD5 hashing for login credentials increases the risk of credential cracking, further exacerbating the threat. The vulnerability undermines user trust and can lead to regulatory penalties under GDPR due to inadequate protection of personal data in transit. The lack of availability impact means services remain operational, but the integrity and confidentiality of user data are critically compromised. The threat is heightened in environments with widespread use of public or insecure networks, common in urban European settings and among mobile users.

Summary

CVE-2025-65827 identifies a critical security vulnerability in a mobile application that permits cleartext HTTP traffic to all domains, including communication with its backend API server. This configuration flaw violates secure communication principles by allowing data to be transmitted without encryption, exposing sensitive information to interception by any adversary positioned upstream in the network path, such as on public Wi-Fi networks or compromised routers. The vulnerability specifically enables attackers to eavesdrop on authentication tokens transmitted in HTTP requests or to crack the MD5 hash used during login authentication. Since MD5 is a weak hashing algorithm vulnerable to collision and preimage attacks, an attacker can potentially reverse or guess the hash to obtain user credentials. The vulnerability requires no privileges or user interaction, making exploitation straightforward. The CVSS 3.1 score of 9.1 reflects the vulnerability's high impact on confidentiality and integrity, with no impact on availability. The vulnerability is categorized under CWE-319 (Cleartext Transmission of Sensitive Information). Although no exploits have been reported in the wild yet, the risk is significant given the ease of interception and the potential for total account compromise. The absence of patch links suggests that a fix has not yet been publicly released, emphasizing the urgency for developers and organizations to implement mitigations. This vulnerability highlights the critical importance of enforcing HTTPS-only communication, using strong cryptographic primitives, and securing authentication tokens against interception and replay attacks.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 17 Dec 2025, 22:12 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats