CVE-2025-64772: Sony INZONE Hub · Uncontrolled Search Path Element
Affects Sony INZONE HubSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Sony Corporation INZONE Hub | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-64772, European organizations should implement the following specific measures: 1) Restrict execution of the INZONE Hub installer to trusted administrators or controlled environments to minimize exposure to untrusted users. 2) Employ application whitelisting and code integrity policies to prevent unauthorized DLLs from loading during installation. 3) Monitor system and application logs for unusual DLL loading behavior or installer execution patterns indicative of exploitation attempts. 4) Educate users about the risks of running installers from untrusted sources and the importance of verifying software authenticity. 5) Isolate systems running INZONE Hub installers from critical network segments to limit potential lateral movement. 6) Prepare for patch deployment by inventorying affected versions and establishing rapid update procedures once Sony releases official patches. 7) Use endpoint detection and response (EDR) tools to detect suspicious activities related to DLL hijacking or privilege escalation. 8) Consider deploying sandbox environments for testing installers before production deployment. These targeted actions go beyond generic advice by focusing on controlling installer execution, monitoring DLL loading, and preparing for timely patching.
Description
The installer of INZONE Hub 1.0.10.3 to 1.0.17.0 contains an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries. As a result, arbitrary code may be executed with the privilege of the user invoking the installer.