cve.bz

CVE-2026-50077 blackberry ltd: Out-of-bounds Write

7.7 highEPSS 0.1%

High (7.7) in blackberry ltd. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
Assigned by
blackberry (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-50077 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50077?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50077?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50077 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-50077

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-50077](https://cve.bz/cve/badge/CVE-2026-50077.svg)](https://cve.bz/cve/CVE-2026-50077)

HTML:

<a href="https://cve.bz/cve/CVE-2026-50077"><img src="https://cve.bz/cve/badge/CVE-2026-50077.svg" alt="CVE-2026-50077"></a>

Affected

  • blackberry ltd:qnx hypervisor
  • blackberry ltd:qnx hypervisor for safety

Versions

From the CNA's record in the CVE List.

ProductAffected
BlackBerry Ltd QNX Hypervisorcpe:2.3:a:blackberry:qnx_hypervisor:8.0:*:*:*:*:*:*:*
BlackBerry Ltd QNX Hypervisorcpe:2.3:a:blackberry:qnx_hypervisor:2.2:*:*:*:*:*:*:*
BlackBerry Ltd QNX Hypervisorcpe:2.3:a:blackberry:qnx_hypervisor:2.0:*:*:*:*:*:*:*
BlackBerry Ltd QNX Hypervisor for Safetycpe:2.3:a:blackberry:qnx_hypervisor_for_safety:8.0:*:*:*:*:*:*:*
BlackBerry Ltd QNX Hypervisor for Safetycpe:2.3:a:blackberry:qnx_hypervisor_for_safety:2.2:*:*:*:*:*:*:*
BlackBerry Ltd QNX Hypervisor for Safetycpe:2.3:a:blackberry:qnx_hypervisor_for_safety:2.0:*:*:*:*:*:*:*

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON