CVE Tools

CVE-2026-59133

Microsoft High Performance Computing (HPC) Pack Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 58th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether your organization runs Microsoft High Performance Computing (HPC) Pack and identify its installed version.
  2. If the version is older than 2.0.1193.0, plan an upgrade to 2.0.1193.0 as the fix.
  3. If you can’t upgrade immediately, restrict who can reach HPC Pack from the network (limit access to only required, trusted accounts and hosts).
  4. Review account access: ensure the minimum necessary privileges for accounts that can authenticate to the system running HPC Pack.

What it is

From the CVE record

Execution with unnecessary privileges in Microsoft High Performance Computing (HPC) Pack allows an authorized attacker to elevate privileges over a network.

In plain language

Written by AI from the record

CVE-2026-59133 is an elevation-of-privilege flaw in Microsoft High Performance Computing (HPC) Pack where someone with a low-privilege network account can take higher control over the software; if you run this on a network with user accounts, you should act now.

Authenticated low-privilege users can exploit a Microsoft High Performance Computing (HPC) Pack process-handling weakness to gain unauthorized higher-level permissions via network access, enabling full control of the affected HPC Pack software.

If you're affected

  • Full control of HPC software
  • Service disruption
  • Data and capability takeover
  • Wider network impact

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS58th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.9% chance of exploitation activity in the next 30 days, which ranks it in the 58th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 17 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows App, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store