QNX HYPERVISOR · CVE-2026-50077 · Infrastructure
FIX → 8.0.4 Update 2 · 2.2.10 · 2.2.11 +2 ✓ verified
BlackBerry QNX advisory QNX-2026-006: invalid memory access through the MSI-X table in the QNX Virtual Machine (QVM) lets a privileged attacker in a guest cause memory corruption, information disclosure or a QVM crash (CVSS 7.7, CWE-787). QNX is not aware of exploitation; no mitigations or workarounds exist, only the update.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems running QNX Hypervisor or QNX Hypervisor for Safety, where a guest VM could run untrusted or compromised code. The attacker must already run code in the guest with enough privilege to manipulate the MSI-X table, and QNX rates complexity high. Teams without QNX hypervisor guests can skip it.
Not affected if no-qnx-hypervisor, no-untrusted-guest-code
Who cares embedded, guest-escape, hypervisor, local, qnx, qvm, virtualization
8.0.4 Update 1 and earlier, 2.2.9 and earlier (Hypervisor), 2.2.10 and earlier (for Safety), 2.0.8 and earlier (Hypervisor), 2.0.2 and earlier (for Safety)Invalid Memory Access via the MSI-X table in QVM could allow an attacker in the guest to execute arbitrary code in the QVM to cause memory corruption, information disclosure or a crash of the QVM.
This page as .md · .json · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 8.0.4 Update 2 · 2.2.10 · 2.2.11 +2
8.0.4 Update 2 or 2.2.10 or 2.0.9; QNX Hypervisor for Safety 8.0.4 Update 2 or 2.2.11 or 2.0.3