Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Out-of-Bounds Write (CVE‑2026‑84854) in Siemens PSS(R)SINCAL’s WibuKey Driver Triggers DoS

A CVE‑2026‑84854 out‑of‑bounds write flaw in the WibuKey licensing driver bundled with Siemens PSS(R)SINCAL can cause a system crash when the legacy dongle mode is enabled. The issue affects versions 21.5, 22.0 and 22.5 (< 22.5.5) and is rated CVSS 7.0 (High). It highlights the importance of third‑party component monitoring and audit‑ready remediation evidence for control‑assurance programs.

Verisq™ Intelligence · 📅 October 23, 2026 · 📰 cisa.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
6 sector(s)
✅
Actions
4 recommended
📰
Source
cisa.gov

Out-of-Bounds Write (CVE‑2026‑84854) in Siemens PSS(R)SINCAL’s WibuKey Driver Causes DoS

What It Is – The WibuKey licensing dongle driver bundled with Siemens PSS(R)SINCAL contains an out‑of‑bounds write flaw (CVE‑2026‑84854). When the product is configured to use the legacy WibuKey dongle, crafted input can corrupt a kernel buffer, leading to a crash and denial‑of‑service.

Exploitability – No public exploit code has been released, but the vulnerability is rated CVSS v3.1 7.0 (High) and can be triggered locally by an attacker with access to the licensing interface.

Affected Products – Siemens PSS(R)SINCAL V21.5 (all), V22.0 (all), and V22.5 (versions < 22.5.5).

Why It Matters for Trust & Control Assurance

  • Third‑party component oversight – The flaw lives in a vendor‑supplied licensing module, underscoring the need for continuous monitoring of external code and proof of due‑diligence.
  • Evidence of patch posture – Demonstrating that you have applied Siemens’ interim mitigations (or disabled legacy dongles) provides audit‑ready evidence of a controlled environment.
  • Defensible incident response – Knowing the exact control (license‑management process) that can be abused helps map the incident to a single control objective (secure configuration and vendor‑risk management) that satisfies many frameworks (e.g., NIST CSF 2.0, ISO 27001).

Recommended Actions

  1. Inventory all PSS(R)SINCAL installations and identify those using the legacy WibuKey dongle.
  2. Apply Siemens‑provided patches or, where unavailable, follow the vendor’s mitigation guidance (e.g., disable the legacy dongle).
  3. Update your third‑party risk register to reflect the new vulnerability and record remediation status as continuous assurance evidence.
  4. Incorporate the licensing component into your regular vulnerability‑scanning and configuration‑baseline checks.

Source: CISA Advisory ICS‑A‑26‑295‑06

📰 Original Source
https://www.cisa.gov/news-events/ics-advisories/icsa-26-295-06 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →