CVE-2025-55232: Microsoft HPC Pack 2019 · Deserialization of Untrusted Data
Affects Microsoft HPC Pack 2019Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.1% chance of exploitation in 30 days – higher than 81% 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:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Microsoft HPC Pack 2019 | Affected
| Fixed in– |
AI-suggested
To mitigate the risk posed by CVE-2025-55232, organizations should take the following specific actions: 1) Immediately restrict network access to Microsoft HPC Pack services by implementing firewall rules and network segmentation to limit exposure only to trusted management networks and users. 2) Monitor network traffic and application logs for unusual deserialization activity or unexpected serialized data payloads, using intrusion detection systems (IDS) and endpoint detection and response (EDR) tools configured to detect exploitation attempts. 3) Apply the official security patch from Microsoft as soon as it becomes available; maintain close communication with Microsoft security advisories for updates. 4) If patching is delayed, consider temporary workarounds such as disabling or isolating vulnerable HPC Pack components that handle deserialization or deploying application-layer gateways to inspect and filter serialized data inputs. 5) Conduct a thorough inventory of HPC Pack deployments and verify versions to identify affected systems. 6) Educate HPC administrators and security teams about the risks of deserialization vulnerabilities and the importance of secure coding and input validation practices. 7) Implement strict access controls and multi-factor authentication for HPC management interfaces to reduce the risk of lateral movement post-exploitation. 8) Regularly back up critical HPC configuration and data to enable recovery in case of compromise. These measures, combined with vigilant monitoring and timely patching, will significantly reduce the likelihood and impact of exploitation.
Description
Deserialization of untrusted data in Microsoft High Performance Compute Pack (HPC) allows an unauthorized attacker to execute code over a network.