BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-81572High confidence

Local Privilege Escalation in CodeMeter Runtime on Windows

wibu-systems-ag · codemeter-runtime

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 28 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs wibu-systems-ag codemeter-runtime and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
sca-2026-0011 · CSAF 2.0 · revision 2 · finalSICK PSIRTCVE-2026-81572
20 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • Sentio Creator < 2026.3
  • SICK Safety Designer >= SD2025.03 V1.20.2141
  • SICK Stream Editor all versions
  • SICK Sentio Compose < 2.1.0
  • SICK CODE-LOC all versions
  • SICK LiDAR-LOC all versions
  • SICK APU0G00 with Image Version 1.0.0.7 and Image ID 30
  • SICK APU0G00 with Image Version 1.0.0.2 and Image ID 38
  • SICK APU0G50 with Image Version 1.0.0.2 and Image ID 38
  • SICK APU0G50 with Image Version 1.0.0.1 and Image ID 45
  • SICK APU0G03 with Image Version 1.0.0.1 and Image ID 41
  • SICK APU0G03 with Image Version 1.0.0.2 and Image ID 36
Summary
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.
Remediation
Customers are strongy recommended to update the Codemeter Runtime to the latest version (>= 9.10). The software can be downloaded directly on the Wibu Systems website: https://www.wibu.com/de/support/anwendersoftware/anwendersoftware.html
3BHS973333 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2026-81572
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ABB AC 800PEC <5.4.5.2
  • ABB AC 800PEC ARM /all
  • ABB AC 800PEC Tool /all
  • ABB AC 800PEC Tool Cheetah /all
  • ABB Control Terminal (xCT) /all
Summary
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.
Remediation
The problem is corrected by Wibu in the following product versions: - CodeMeter Runtime 8.41a - CodeMeter Runtime 9.10 ABB recommends that customers apply the update at their earliest convenience and install the version compatible with their operating system. Both versions are available for download from the Wibu download site and can be updated independent of the tool installation: https://www.wibu.com/support/user/user-software.html. An updated version of CodeMeter Runtime containing the fixes will be integrated into the following tool versions: - AC 800PEC: Version 5.4.5.2 - AC 800PEC ARM: Version 3.0.0.0 (Expected by Q1 2027) - AC 800PEC Tool: Not planned, in classic lifecycle phase - AC 800PEC Tool Cheetah: Version 3.0.0.0 (Expected by Q1 2027) - Control Terminal (xCT): Not planned, in classic lifecycle phase
2NGA003144 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2026-81572
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • WIBU-Systems CodeMeter Runtime <8.41a installed with ABB AbilityTM zenon <=14
Summary
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.
Remediation
ABB recommends the following mitigation measures: - Update the WIBU-Systems CodeMeter Runtime to version 8.41a or later. - The latest CodeMeter Runtime software is available from the WIBU-Systems download page: User Software - Wibu-Systems, please see the References section for the corresponding link. - Where upgrading is not feasible, ABB recommends that asset owners perform a risk assessment and implement compensating controls such as network isolation, access restrictions, and enhanced monitoring of affected systems. ABB recommends that customers apply the update at earliest convenience. The vulnerabilities associated with CVE-2026-81573, CVE-2026-81574, CVE-2026-81575 and CVE-2026-81576 are exploitable only when the WIBU-Systems CodeMeter Runtime is configured as a network server, which is not the de-fault configuration. The CVE-2026-81572 vulnerability requires local access to the affected Windows system and execution by a low-privileged user. Consequently, systems with restricted local access, proper privilege management, and limited network exposure are less likely to be successfully compromised. Refer to section “General security recommendations” for further advise on how to keep your system secure.
3ADR011572 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2026-81572
4 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ABB Automation Builder >2.10.0
  • ABB Drive Application Bulder /all
  • ABB Virtual Drive >1.5.1
  • ABB Virtual Drive Plus >1.70
Summary
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.
Remediation
The problem is corrected by Wibu in the following product versions: - CodeMeter Runtime 8.41a - CodeMeter Runtime 9.10 ABB recommends that customers apply the update at earliest convenience. Both versions are available for download from the Wibu download site and can be updated independent of the tool installation: https://www.wibu.com/support/user/user-software.html An updated version of CodeMeter Runtime containing the fixes will be integrated into the following tool versions: - Automation Builder: Version 2.10.0 (expected by Q1/2027) - Drive Application Bulder: not planned, will be transferred to the Classic lifecycle phase end of Q3/2026 - Virtual Drive: Version 1.5.1 - Virtual DrivePlus: Version 1.70 (expected by Q4/2026)
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-66979

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

What

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.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Link Resolution Before File Access ('Link Following') → gain additional privileges
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following'). The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Privilege escalationCWE-59
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-66979Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3004Wibu-Systems CodeMeter Runtime: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Wibu-Systems CodeMeter Runtime ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Berechtigungen zu erweitern und Administratorrechte zu erlangen oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 2 Sept 2026, published on 2 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0333Kwetsbaarheden verholpen in CodeMeter Runtime van Wibu-Systems

CodeMeter Runtime versions 8.40 to before 8.41a and 9.00 to before 9.10 contain a vulnerability involving predictable temporary files and improper NTFS reparse point checks, enabling local attackers to delete files with System privileges and escalate privileges.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Aug 2026 · Last source change 28 Aug 2026, 16:52 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-27
European sourceENISA EUVD · EUVD-2026-66979
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    SICK Sentio Creator all versions; SICK Safety Designer >= SD2025.03 V1.20.2141; SICK Stream Editor all versions; SICK Sentio Compose < 2.1.0; SICK APU0G00 with Image Version 1.0.0.7 and Image ID 30; SICK APU0G00 with Image Version 1.0.0.2 and Image ID 38; SICK APU0G50 with Image Version 1.0.0.2 and Image ID 38; SICK APU0G50 with Image Version 1.0.0.1 and Image ID 45; SICK APU0G03 with Image Version 1.0.0.1 and Image ID 41; SICK APU0G03 with Image Version 1.0.0.2 and Image ID 36; SICK APU3F00 with Image Version 1.0.0.0 and Image ID 27; SICK APU3F00 with Image Version 1.0.0.0 and Image ID 46; SICK APU4600 with Image Version 1.1.0.1 and Image ID 18; SICK APU8G00 with Image Version 1.0.0.11 and Image ID 15; SICK APU8G00 with Image Version 1.0.0.2 and Image ID 44; SICK APU8G20 with Image Version 1.0.0.2 and Image ID 29; SICK APU8G20 with Image Version 1.0.0.2 and Image ID 32; SICK PLB with all firmware versions · Fixed: SICK Sentio Compose 2.1.0
    After
    Sentio Creator < 2026.3; SICK Safety Designer >= SD2025.03 V1.20.2141; SICK Stream Editor all versions; SICK Sentio Compose < 2.1.0; SICK CODE-LOC all versions; SICK LiDAR-LOC all versions; SICK APU0G00 with Image Version 1.0.0.7 and Image ID 30; SICK APU0G00 with Image Version 1.0.0.2 and Image ID 38; SICK APU0G50 with Image Version 1.0.0.2 and Image ID 38; SICK APU0G50 with Image Version 1.0.0.1 and Image ID 45; SICK APU0G03 with Image Version 1.0.0.1 and Image ID 41; SICK APU0G03 with Image Version 1.0.0.2 and Image ID 36; SICK APU3F00 with Image Version 1.0.0.0 and Image ID 27; SICK APU3F00 with Image Version 1.0.0.0 and Image ID 46; SICK APU4600 with Image Version 1.1.0.1 and Image ID 18; SICK APU8G00 with Image Version 1.0.0.11 and Image ID 15; SICK APU8G00 with Image Version 1.0.0.2 and Image ID 44; SICK APU8G20 with Image Version 1.0.0.2 and Image ID 29; SICK APU8G20 with Image Version 1.0.0.2 and Image ID 32; SICK PLB with all firmware versions · Fixed: SICK Sentio Compose 2.1.0; Sentio Creator 2026.3
    SICK PSIRT ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    8.40 < 8.41a; 9.00 < 9.10 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    8.40 < 8.41a; 9.00 < 9.10 · Fixed: The problem is corrected by Wibu in the following product versions: - CodeMeter Runtime 8.41a - CodeMeter Runtime 9.10 ABB recommends that customers apply the update at their earliest convenience and install the version compatible with their operating system. Both versions are available for download from the Wibu download site and can be updated independent of the tool installation: https://www.wibu.com/support/user/user-software.html. An updated version of CodeMeter Runtime containing the fixes will be integrated into the following tool versions: - AC 800PEC: Version 5.4.5.2 - AC 800PEC ARM: Version 3.0.0.0 (Expected by Q1 2027) - AC 800PEC Tool: Not planned, in classic lifecycle phase - AC 800PEC Tool Cheetah: Version 3.0.0.0 (Expected by Q1 2027) - Control Terminal (xCT): Not planned, in classic lifecycle phase
    ABB Product Security Incident Response Team (PSIRT) ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    ABB Product Security Incident Response Team (PSIRT) ↗
  4. Public exploit evidencePublic exploit evidence changed from Public exploit reference to No public exploit.
    Before
    Public exploit reference
    After
    No public exploit
    CVE.org ↗
  5. ENISA EUVD mappingEUVD-2026-66979 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-66979"}
    ENISA EUVD ↗
  6. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    CVE.org ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-66979↗Vendor CSAF · SICK PSIRT↗ABB Product Security Incident Response Team (PSIRT) security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-81572 · cve.blacktree.nl