VulnerabilityPublished 24 Nov 2025

CVE-2025-63434: CVE-2025-63434 is a high-severity

Source CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: 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: 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: 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 24 Nov 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

To mitigate this vulnerability, organizations should: 1) Immediately restrict network access to update servers and ensure updates are downloaded only from trusted, verified sources. 2) Monitor network traffic for suspicious update metadata or unexpected update package downloads. 3) Work with Xtooltech to obtain and apply any forthcoming patches or updated app versions that implement cryptographic signature verification of update packages. 4) If patching is not immediately possible, consider disabling automatic updates or update functionality until a secure version is available. 5) Employ mobile device management (MDM) solutions to control app permissions and monitor app behavior on diagnostic devices. 6) Conduct regular security audits of diagnostic tools and isolate them from critical networks to limit lateral movement in case of compromise. 7) Educate staff about the risks of connecting diagnostic devices to untrusted networks or sources. These steps go beyond generic advice by focusing on controlling update sources, monitoring for anomalies, and isolating affected devices.

Description

CVE-2025-63434 is a high-severity vulnerability in the update mechanism of the Xtooltech Xtool AnyScan Android application (version 4.40.40 and prior). The app downloads and extracts update packages containing executable code without verifying their cryptographic integrity or authenticity. This flaw allows an attacker who can manipulate the update metadata to serve malicious packages that the app will accept and execute, resulting in arbitrary code execution. The vulnerability requires low privileges but no user interaction, making exploitation feasible in network-exposed environments. Although no known exploits are currently reported, the impact on confidentiality, integrity, and availability is severe. European organizations using this application, especially in automotive diagnostics or related fields, are at risk. Mitigation involves implementing cryptographic signature verification for update packages and restricting update metadata sources. Countries with significant automotive industries and high Android device usage, such as Germany, France, Italy, Spain, and the UK, are most likely to be affected.

Impact

For European organizations, especially those in automotive diagnostics, repair, and maintenance sectors using the Xtool AnyScan Android app, this vulnerability poses a significant risk. Exploitation could lead to unauthorized code execution on diagnostic devices, potentially compromising sensitive vehicle data, customer information, and internal networks if these devices are connected to corporate infrastructure. The integrity of diagnostic results could be undermined, leading to incorrect vehicle assessments or safety risks. Additionally, attackers could use compromised devices as footholds to pivot into broader enterprise networks, threatening confidentiality and availability of critical systems. The lack of cryptographic verification in updates increases the risk of supply chain attacks, which are particularly concerning for organizations relying on trusted software tools. Given the high CVSS score and ease of exploitation, the threat could disrupt operations and damage organizational reputation.

Summary

CVE-2025-63434 identifies a critical security weakness in the update mechanism of the Xtooltech Xtool AnyScan Android application, version 4.40.40 and earlier. The vulnerability stems from the application's failure to perform cryptographic integrity and authenticity checks on downloaded update packages. Specifically, the app downloads update packages containing executable code and extracts them without verifying digital signatures or hashes. This design flaw corresponds to CWE-494 (Download of Code Without Integrity Check). An attacker capable of controlling or intercepting the update metadata—such as through a man-in-the-middle attack or compromised update server—can serve a malicious update package. The application will accept, extract, and eventually execute this malicious code, leading to arbitrary code execution on the device. The CVSS v3.1 base score is 8.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and no user interaction required. The vulnerability requires only low privileges (PR:L), meaning an attacker with limited access could exploit it remotely (AV:N). No patches or exploit code are currently publicly available, but the risk remains significant due to the nature of the flaw and the widespread use of the application in automotive diagnostics. This vulnerability could allow attackers to gain persistent control over affected devices, steal sensitive data, or disrupt operations.

CWE-494Download of Code Without Integrity Check (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.
Implementation
Perform proper forward and reverse DNS lookups to detect DNS spoofing.
Architecture and Design · Operation
Encrypt the code with a reliable encryption scheme before transmitting.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.2 (opens in a new tab)
V10.3.1 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
Malicious Software Download (opens in a new tab)
Malicious Software Update (opens in a new tab)
Malicious Automated Software Update via Redirection (opens in a new tab)
Malicious Manual Software Update (opens in a new tab)
Open-Source Library Manipulation (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 1 Dec 2025, 17:45 UTC

WeaknessesCWE-494

Technical details

References

Community reviews

Related threats