cve.bz

CVE-2026-50079 blackberry ltd

3.3 lowEPSS 0.08%

Low (3.3) in blackberry ltd. EPSS 0.08% estimated probability of exploitation activity in the next 30 days.

On this page
Time-of-check Time-of-use (TOCTOU) Race Condition in the virtio network virtual device could allow an attacker in the guest to manipulate the virtual network device causing a crash of the QVM.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.08% estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
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-50079 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50079?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50079?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-50079 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-50079

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-50079](https://cve.bz/cve/badge/CVE-2026-50079.svg)](https://cve.bz/cve/CVE-2026-50079)

HTML:

<a href="https://cve.bz/cve/CVE-2026-50079"><img src="https://cve.bz/cve/badge/CVE-2026-50079.svg" alt="CVE-2026-50079"></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:*:*:*:*:*:*:*

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

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