NTFS reparse-point flaw enables local privilege escalation in WIBU-Systems CodeMeter Runtime

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-81572?

CVE-2026-81572 is a vulnerability classified as Improper Link Resolution Before File Access, affecting codemeter-runtime (affected versions: 8.40 – < 8.41a and 9.00 – < 9.10). This vulnerability is rated High, with a CVSS score of 7.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

In CodeMeter Runtime from version 8.40 to (excluding) 8.41a and 9.00 to (excluding) 9.10, cmu.exe --create-io --file C: creates a predictable temporary file under C:\CM-Stick. The directory and file paths are not properly checked for NTFS reparse points, such as junctions or symbolic links, before file operations are performed. A local attacker can create a junction at the temporary file that points to an arbitrary system path. Because CodeMeter Runtime runs with System privileges, this could allow arbitrary files to be deleted with System privileges and potentially enable local privilege escalation.

Affected products and scope

  • CodeMeter Runtime on Windows, 8.x branch: the structured CNA record identifies versions from 8.40 through but excluding 8.41a as affected. The vendor advisory presents this branch as 8.40 - 8.41 in its affected table and marks >= 8.41a as fixed, so installations reporting an 8.41 build require exact build verification.
  • CodeMeter Runtime on Windows, 9.x branch: versions from 9.00 through but excluding 9.10 are affected; the vendor identifies >= 9.10 as fixed.
  • The normalized record sets the default status to unaffected for versions outside those ranges. It does not identify another affected CodeMeter Runtime branch.
  • Third-party products embedding CodeMeter Runtime must be assessed by the runtime version actually installed, because the host product version alone does not prove that the runtime is fixed.

Technical details

WIBU-Systems CodeMeter Runtime uses cmu.exe --create-io --file C: to create a predictable temporary file under C:\CM-Stick. The directory and file paths are not adequately checked for NTFS reparse points, including junctions and symbolic links, before file operations occur. A low-privileged local attacker can place a junction at the temporary file and redirect the operation to an arbitrary system path. Public research describes CodeMeter.exe as running under NT AUTHORITY\SYSTEM and being controllable through cmu.exe, creating a privileged arbitrary-file-deletion primitive. The record does not establish every internal API call or every file operation affected, but it confirms the missing link validation and the arbitrary file deletion consequence.

Exploitability

The flaw requires local access to a Windows host running an affected CodeMeter Runtime installation. The normalized record describes low required privileges, no user interaction, and low attack complexity; it does not describe the core flaw as directly reachable over the network. Public exploitation evidence is mixed: the normalized record sets public_exploit to false, while the public Shelltrail research documents a proof of concept and a path to SYSTEM. A returned CISA ADP assessment recorded exploitation as none at the time of that assessment; this is time-scoped and does not establish that abuse has never occurred or will not occur later. The complete privilege-escalation chain also depends on Windows Installer behavior and host configuration, so every vulnerable installation should not be assumed to yield SYSTEM automatically.

Technical impact

The confirmed direct outcome is arbitrary file deletion with System privileges through improper handling of paths containing reparse points. This can remove or alter important resources on the same host, affecting integrity and availability and potentially enabling local privilege escalation. Public research describes a chain that can turn the file-deletion primitive into SYSTEM, but that chain depends on Windows Installer behavior and specific operating-system or configuration conditions. The flaw is not described as a remotely reachable attack path and does not by itself establish impact on other hosts. The supplied evidence does not identify a breach, data theft, or direct impact on the safety functions of every product that uses CodeMeter.

Business impact

  • A compromised local account or malware already running on the host may use the flaw to trigger file operations with System privileges.
  • Arbitrary file deletion can damage operating-system resources, configuration, or application files, causing loss of system integrity or availability.
  • If the escalation chain succeeds, the attacker may cross the local privilege boundary and modify protected resources on the same host.
  • Systems dependent on CodeMeter for licensing may experience service or application disruption if relevant files are deleted, but the available evidence does not confirm a particular outage, data breach, or campaign.
  • Impact on embedded or industrial products must be assessed per product because the surrounding product version does not by itself establish the CodeMeter Runtime version or the resulting operational effect.

Remediation

  1. Upgrade CodeMeter Runtime installations in the 8.x branch to 8.41a or a later 8.x release covered by the vendor's fixed range. For the 9.x branch, upgrade to 9.10 or a later 9.x release covered by the fixed range.
  2. For software or devices embedding CodeMeter Runtime, apply the product vendor's update that ships a fixed runtime and verify the installed runtime after deployment.
  3. Inventory standalone installations, license servers, and system images so that no old cmu.exe or CodeMeter service remains in an overlooked location. Do not infer safety from the surrounding product version alone.
  4. The record and vendor advisory do not provide a specific workaround that replaces patching. If immediate updating is not possible, restrict untrusted local accounts and isolate sensitive hosts as temporary precautions, not as a confirmed fix.
  5. After updating, verify the versions of cmu.exe and CodeMeter.exe, inspect C:\CM-Stick, and address unexpected reparse points before returning the host to normal operation.

Detection

  1. Inventory Windows hosts and embedded products that include CodeMeter Runtime, recording the exact runtime branch and build rather than relying only on the surrounding product name.
  2. Check version metadata for cmu.exe, the CodeMeter.exe service, and the actual installation path to identify vulnerable copies or stale binaries left after an update.
  3. Inspect C:\CM-Stick for unexpected junctions, symbolic links, or other reparse points at temporary files created by CodeMeter. This is a precautionary check, not a vendor-confirmed IOC.
  4. Review file-system, EDR, and Windows telemetry for reparse-point creation, unusual deletion activity, or CodeMeter operations involving C:\CM-Stick. The supplied sources do not establish a specific log event or IOC.
  5. When assessing the published escalation chain, review the DisableMSI policy and whether per-user MSI installation is permitted on the host. This helps assess the documented chain but is not a substitute for updating CodeMeter Runtime.
Sources (15)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.