CVE-2025-63701: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 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 2026-10-25.
What to do
AI-suggested
1. Restrict local access to systems running the Advantech TP-3250 printer driver to trusted personnel only. 2. Monitor and audit local user activities on affected systems to detect suspicious behavior. 3. Implement application whitelisting to prevent unauthorized execution of code in user space. 4. Use endpoint detection and response (EDR) tools to identify anomalous memory corruption or crashes related to the driver. 5. Coordinate with Advantech for timely release and deployment of patches or updated driver versions. 6. If patching is delayed, consider isolating affected devices on segmented networks to limit lateral movement. 7. Educate users about the risks of running untrusted applications locally that might trigger the vulnerability. 8. Regularly review and update printer driver inventories to identify and remediate vulnerable versions.
Description
A heap corruption vulnerability exists in the Advantech TP-3250 printer driver's DrvUI_x64_ADVANTECH.dll (v0.3.9200.20789) when DocumentPropertiesW() is called with a valid dmDriverExtra value but an undersized output buffer. The driver incorrectly assumes the output buffer size matches the input buffer size, leading to invalid memory operations and heap corruption. This vulnerability can cause denial of service through application crashes and potentially lead to code execution in user space. Local access is required to exploit this vulnerability.