dbcve.org
Hpc PackApplication · Microsoft

CVE-2025-55232

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 6.3.8352 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of untrusted data in Microsoft High Performance Compute Pack (HPC) allows an unauthorized attacker to execute code over a network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a deserialization vulnerability in Microsoft High Performance Compute Pack where untrusted data is insecurely processed, allowing an unauthenticated remote attacker to execute arbitrary code on affected systems.

MitigationApply vendor patches immediately; until then, restrict network access to HPC services and disable any unnecessary exposed interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hpc PackApplication
Affected:< 6.3.8352

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Microsoft HPC Pack is installed
    Check installed programs list via Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell and look for 'HPC Pack' in the name
    Affected if Microsoft HPC Pack appears in the installed programs list
  2. Retrieve the installed HPC Pack version
    Open Programs and Features, find Microsoft HPC Pack in the list, and note the version shown in the Version column; alternatively, check the registry key HKLM\SOFTWARE\Microsoft\HPC\Install for a Version or DisplayVersion value
    Affected if A version number is found that is lower than 6.3.8352
  3. Confirm HPC services are running
    Open Services console (services.msc) or run 'Get-Service | Where-Object {$_.Name -like "*HPC*"}' in PowerShell to list HPC-related services
    Affected if Any HPC-related services are in a Running state, indicating the vulnerable component is active
  4. Check for exposed HPC network listeners
    Run 'netstat -an | findstr LISTENING' and look for ports commonly used by HPC Pack (default HPC communication ports such as 80, 443, 8080, or custom ports configured during HPC Pack setup); also check IIS Manager for HPC-related sites if IIS is installed
    Affected if Network listeners are bound to HPC service ports, meaning the deserialization endpoint is network-accessible

The system is affected if Microsoft HPC Pack is installed with a version lower than 6.3.8352 and HPC services are running or exposing network interfaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.3.8352 or later
Fixed in 6.3.8352
Interim mitigation

Apply vendor patches immediately; until then, restrict network access to HPC services and disable any unnecessary exposed interfaces.

Recommended fix Moderate confidence

Microsoft HPC Pack version 6.3.8352 or later

  1. Download Microsoft HPC Pack version 6.3.8352 or later from the official Microsoft Download Center or through your Microsoft licensing portal
  2. Review the HPC Pack 6.3.8352 release notes for any known installation prerequisites
  3. Ensure you have backups of your HPC cluster configuration and job schedules
  4. Install the upgrade on the HPC Pack head node first, following standard Microsoft installation procedures
  5. After upgrading the head node, update compute nodes as needed to maintain cluster consistency
  6. Verify the installation by checking the HPC Pack version in Cluster Manager or via PowerShell Get-HPCCluster cmdlet
  7. Test critical HPC job submission and execution to confirm normal operations
Caveat Review release notes for any configuration or API changes that may affect existing job templates or automation scripts; test in non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hpc Pack Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55232 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data