Wibu-systems-ag vulnerabilities
We track 8 vulnerabilities in Wibu-systems-ag products across 2 products. 8 are rated high or critical, and none are known to be exploited. The most recent was published on October 6, 2026.
Latest Wibu-systems-ag vulnerabilities
- 7.0 High severity
wibukey: Out-of-bounds Write
In the WibuKey driver for Windows below Version 6.72, insufficient validation of user input when calculating the size of a kernel buffer could cause small amounts of data to be written outside the intended kernel buffer. This can lead to a system crash. Under
- 8.8 High severity
wibukey: Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper validation of memory boundaries in WibuKey64.sys of WibuKey up to 6.70 for Windows can be exploited by an attacker by setting the pointers outside the scope of the program. This usually results in a denial of service, yet we cannot rule out the possib
- 8.8 High severity
wibukey: Write-what-where Condition
In WibuKey for Windows before version 6.71, an untrusted pointer dereference in the WibuKey2_64.sys kernel driver for 64-bit Windows allows an attacker to exploit a write-what-where primitive, enabling local privilege escalation. This can be leveraged to execu
- 7.7 High severity
codemeter-runtime: Authorization Bypass Through User-Controlled Key
If configured as a server, CodeMeter Runtime before versions 8.41a and 9.10 issues handles per connection and relies on a cryptographically weak SID as sole authenticator. An attacker can brute-force the SID, recover another session's handle number, and read l
- 7.5 High severity
codemeter-runtime: Improper Handling of Length Parameter Inconsistency
If configured as a server, CodeMeter Runtime before versions 8.41a and 9.10 accepts requests with opcode 0x5e, which contain the data length and the data itself. Missing bounds checking on the data length value can lead to out of bounds reads, causing a segmen
- 8.2 High severity
codemeter-runtime: Use of Externally-Controlled Format String
In CodeMeter Runtime before versions 8.41a and 9.10, the logger does not sanitize input strings in certain cases, allowing an attacker to inject printf-style format specifiers. This can be used to reliably crash CodeMeter and disclose sensitive information suc
- 8.6 High severity
codemeter-runtime: Improper Access Control
If CodeMeter Runtime before 8.41a or 9.10 is configured as a server, the configuration command handler does not enforce network- origin restrictions. Commands intended only for local or same-network clients can therefore be executed by arbitrary remote peers.
- 7.8 High severity
codemeter-runtime: Improper Link Resolution Before File Access
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